We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy. Image for the cookie policy date

Memory leak in XPThemes (2.0.5.0 & 2.1.0.9)

Each time a new ComboBoxAdv ( perhaps, any themed control ) is created multiple instance of ThemedDropDownButtonDrawing objects are used as a key in the XPThemes.htThemedControlDrawing Hashtable. The Hashtable is static and it only gets recycled when the app closes. Curiously enough, commenting out this call doesn''t seem to break anything.

2 Replies

SH Simon Hewitt June 9, 2006 05:51 AM UTC

I too have seen this in v3.301. DropDownButton is not disposable but its constructor creates a ThemedDropDownButtonDrawing (which derives from ThemedControlDrawing and gets put into the static Hashtable as mentioned below) which *is* disposable but never gets disposed. Any chance of a fix for this?? Cheers Simon >Each time a new ComboBoxAdv ( perhaps, any themed control ) is created multiple instance of ThemedDropDownButtonDrawing objects are used as a key in the XPThemes.htThemedControlDrawing Hashtable. > >The Hashtable is static and it only gets recycled when the app closes. > >Curiously enough, commenting out this call doesn''t seem to break anything. >

Anupama Roy June 9, 2006 12:12 PM UTC

Hi Simon, Thank you for the feedback. I am able to reproduce the memory leak as you have said.We will work on this issue and will keep you informed as soon as it is fixed. Regards, Anu.
Loader.
Live Chat Icon For mobile
Up arrow icon