How to find leak in user objects

Question

Our .Net 4.0 application has a leak due to which it crashes after prolonged use. After the investigation, I determined that the "user objects" are leaking. The user object is a Windows resource, as described here:

http://msdn.microsoft.com/en-us/library/ms725486%28v=VS.85%29.aspx

Windows allocates 10,000 user objects per process. Other Windows resources, such as GDI objects and descriptors, are persistent while the application is running.

I found a similar question for C ++, where the solution required downloading a package called "workaround" from microsoft reseach - catch? $ 10K.

Using Ant memory profiler, I SUSPECT, this is related to the menu. We use the SyncFusion menu, so the life cycle of the material related to the menu cannot be found by looking at the code. So it could be a bug that SynFusion should solve.

Who has a similar leak using the SyncFusion menu? Ants tell me that some PopupMenu objects are glued together, but Ants does not give information on how to find where the objects are created (and therefore determine where to Dispose them).

The leak / crawl vulnerability mentioned in the SO post link above looks interesting because it seems to be a trap for specific calls to host a USER object.

Suggestions are welcome

Answer 1

if you know that a menu hangs around you, you should be able to list GDI objects for your process and nurf them using DeleteMenu ().

Window

should notify your parent window when pop-up menus are displayed and closed, so this is the perfect place to take snapshots of GDI menu descriptors and delete newer ones.

its pretty brute force and is not recommended for .net, where doing this kind of manipulation with a low level of GDI is probably naughty

I would make a simple test application with the SyncFusion menu to prove it, and if the problem persists, contact your vendor