1.7.2 Leaking Resources (GDI)

[wuacid]

The paint routine on your client is leaking 2 GDI handles per refresh...

though not annoying on the whole, over time this results in a rather unceremonious GUI crash in any windows OS (XP & Vista) and has always been that way as far as I can remember (non-managed code GDI calls don't have a per process cap, so when one maxes out the available GDI memory all further requests by any process including system process are denied)

I haven't tried to pin-point the window or "control" with the paint routine inside the client that is leaking handles, but I probably could if you really needed that information (it would just take a bit).

I just figured I could help you help me –because I get annoyed that it cripples my system after being on for too long, if you require more details or would like me to help you localize the problem, I would recommend emailing me as there is no guarantee I will come back and check this post as I may forget about it. Cheers -c

[Firon]

I'm not seeing this behavior. Can you give us a list of processes with HijackThis? Something else might be causing this.

[wuacid]

try on an x64 machine as I have not verified this behavior in the 32 bit realm myself, but my colleague says that he believes he has the same issue (xp pro 32) and I have seen this behavior myself on vista ultimate 64 and xp 64... however I regret to say that I can't provide you with a process listing, upon reading your post I attempted a shut of all non vital processes to no avail, an off the cuff guess would be that if it is a 64 bit thing something may not be handled right and lost in translation and may require the most recent sdk headers

[Greg Hazel]

More information on when/where would be helpful. I ran a simple leak check and did not catch anything. If you could, running GdiUsage and seeing where the handles accumulate would be helpful.