> Gehua Yang wrote:
>> When I use the basic01_display_image executable to display an image, the
>> memory usage keeps increasing as I zoom in, zoom out, or shift the image
>> around. It will use more and more memory until it crashes.
>> For example, with a color image of dimension 3500x2400, the initial
>> memory usage was 80Mb. After one zoom-out and one zoom-in, it became
>> 150Mb. After the second zoom in & out, it was 190Mb and after the third
>> time, it was 250Mb!!!
>> Windows XP
>> Visual Studio 7
>> CMake 2.0 patch2
>> CVS up-to-date version of VXL
>> VGUI toolkits:
>> vgui : registered 'mfc' 'glut'
>> vgui : initialize 'mfc'
>> Similar memory leak is also observed in Linux+GCC 3.4+GTK2.
> This is one of the problems of not having any decent regression tests for
> vgui. Memory leaks in the other libraries are picked up (if not always
> fixed) by the dashboard. It would be really very useful if someone could
> write an automatic test for vgui.
> Alternatively, can I suggest using valgrind or purify to track down the
> memory leak.
One more comment:
Rolling VGUI back to January 2nd seems to work. Since Jan 2nd the major
changes have been vgui_range_map. Could anyone look into it?