Re: [platform-swt-dev] How to debug GDI object leak

[Steve Northover <Steve_Northover@xxxxxxxxxx>]

That's because this (internal) API takes
a preallocated GDI object.

I used to use DEBUG Windows 98 to check
for leaks but I lost this ability when switching to XP.  I've used
BoundsChecker in the past but it gave tons of false positives making it
hard to find the real problem. This is what Microsoft suggests http://msdn.microsoft.com/msdnmag/issues/01/03/leaks/default.aspx

Michael Scharf <Michael-Scharf@xxxxxx> Sent by: platform-swt-dev-admin@xxxxxxxxxxx 10/27/2003 04:03 PM Please respond to platform-swt-dev

To:        platform-swt-dev@xxxxxxxxxxx         cc:                 Subject:        Re: [platform-swt-dev] How to debug GDI object leak

Randy Hudson wrote:

> I am using M4 and am seeing issues with GDI Objects leaking.  I
have 
> tried using Sleak, but according to it, there are no Images, etc.,
that 
> are being leaked.  Yet, my GDI Object count can grow to 10,000,
and 
> Windows XP will "blue screen" eventually.  Is it possible
that Sleak is 
> not report all resources?

Images created with Image.win32_new do not register with SLeak....

It's supposed to be an internal function and it is not supposed
to be used in SWT code, but if you use it, SLeak will not
trace images created by this function....

Michael


_______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-swt-dev