Certain combinations of show{img,poly,text} and hideimg commands seem to cause huge memory leaks in the v3 client (though apparently not v4). I can watch Graal in the Windows process list and see it incessantly consuming at least 250KB per second. Switching display drivers doesn't stop the problem, but it seems like it might change its speed. Not sure.
The weapon 'Kai_MemoryLeak' on the #gscript server provides a simple test case for the phenomenon.
The only reason I'm using hideimg before showimg is that some image properties are apparently preserved on the indices. If I use a transparent showpoly on index 213 then future polygons on that index will also be transparent. I have to use hideimg to manually reset the properties, or explicitly specify them for each call to showpoly
05-25-2005, 07:50 PM
Threaded Mode