v3 Memory Leak
 

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 :\

I did check this out with Kaimetsu. The problem is in Graal 3, but not Graal 4. Testing the problem in Graal 3, I found Graal's memory usage at about 120,000K in a matter of minutes.

Well then it is not a problem I guess, since v4 will replace the old versions (uses the same codebase, so stuff that is fixed in v4 will also be fixed in the versions for Linux and Mac)

Yeah, that was my impression. Still, I wasn't sure how long it'd take for v4 to roll out, so I thought I should report it.