1

Profiling my .NET Application shows me that there is a big delta in UnmangedMemoryStreams.

It seems they are created from some resource loading.

Anyone has an idea what can cause this loading or how to debug this?

Screenshots from Profiling:

http://imgur.com/a/eO76W

http://imgur.com/a/eO76W

magicandre1981
  • 27,895
  • 5
  • 86
  • 127
Michael Spannbauer
  • 109
  • 2
  • 11
  • What assemblies are you loading? Little code details will help – Dark Knight Jul 25 '17 at 08:43
  • @DarkKnight: It's a big project with lots of assemblies. At meantime i found that a Timer updating a label causes the leak. Maybe this link describes my problem, not sure yet... https://stackoverflow.com/questions/31452443/wpf-textblock-memory-leak-when-using-font – Michael Spannbauer Jul 25 '17 at 11:16
  • even this leaks: ... where CurrentTime (string) is set via Timer - Timer itself is not leaking, it's the XAML thing – Michael Spannbauer Jul 25 '17 at 11:22
  • Yep. FontFamily set by some Style is causing the leak. Style="{x:Null}" does not fix it, FontFamily must be set directly like FontFamily="Arial" on the TextBlock. – Michael Spannbauer Jul 25 '17 at 12:22

1 Answers1

1

Like said in the comments, FontFamily is causing the leak. More details: WPF TextBlock memory leak when using Font

Michael Spannbauer
  • 109
  • 2
  • 11