in the current tip (hopefully; I did a “git stash” and “git pull” which should get the current tip as far as I understand) a component that’s based on FileChooserPreview seems to leak memory:
*** Leaked objects detected: 1 instance(s) of class StringArray
JuceDemo.exe hat einen Haltepunkt ausgelöst.
*** Leaked objects detected: 1 instance(s) of class HeapBlock
JuceDemo.exe hat einen Haltepunkt ausgelöst.
This happens for example in the JuceDemo when you use “‘Load’ file browser with an image preview”.
It doesn’t leak that much, but it’s annoying that the debbuger breaks every time you quit.
I’m using Visual Studio 2008 Express if that’s relevant.
I just updated to the latest tip which is confirmed by ‘git log’ (Thu Jan 26). The leak still occurs as soon as a FilePreviewComponent is given to a FileChooser object.
If line 1347 in WidgetsDemo.cpp (JuceDemo) is changed to
if (fc.browseForMultipleFilesToOpen ())
the assertion in LeakCounter isn’t hit.
Could you put the ‘git log’ in the reporting bugs sticky?