More On Memory Management

[Ommina]

Today I'm officially taking off from my memory management investigations. I need to catch up on some sleep.

But I'd like to toss some comments out there to get a feel if what I'm seeing is normal and can be ignored, or a cause for concern.

sub: I'm seeing several (and by 'several' I mean 'tens of thousands') undisposed instances of System.Windows.Forms.WindowsFormSynchronizationContext objects. About 60 a second. They are being destroyed and collected in gc0, but are ending up in the "undisposed" column. They don't seem to be taking up much space, but there sure is an awful lot of them! Is this normal?

Anybody: There are a number of bitmaps and associated graphics objects (System.Drawing.Bitmap, .Graphics, and .StringFormat most notably) that are also ending up as undisposed. Undisposed bitmaps goes up sharply if I wiggle the mouse around while a popup is active. The same behaviour does not occur if there is no popup going. There is an increase in Private Bytes associated with this wiggling, although it's difficult to get a precise handle on how many. Call it, roughly, 150,000 bytes per two second wiggle session.

A G2 collect doesn't collect them, which I'd expect.

Opening and closing a popup with no controls, just a "PopupBackground" Placement, leads to precisely one undisposed bitmap, again with an associated increase in private bytes.

Again, maybe this normal and I'm chasing down the wrong tree (to shamelessly mix metaphors), but it's suspicious enough for me to bring it up here for others to consider. Should I, somehow, be disposing of the "PopupBackgroud" bitmap somewhere?

JavaWiz: I did find one memory leak in your UiTools, but, honestly, I don't think it would account for much more than a few dozen bytes, so I'm not especially panicking over it.

[sub]

sub: I'm seeing several (and by 'several' I mean 'tens of thousands') undisposed instances of System.Windows.Forms.WindowsFormSynchronizationCon text objects. About 60 a second. They are being destroyed and collected in gc0, but are ending up in the "undisposed" column. They don't seem to be taking up much space, but there sure is an awful lot of them! Is this normal?

I have no idea what they are. Its most likely something .net is using behind the scenes. I cant say I've ever noticed them or any problem steming from their existence.

Anybody: There are a number of bitmaps and associated graphics objects (System.Drawing.Bitmap, .Graphics, and .StringFormat most notably) that are also ending up as undisposed. Undisposed bitmaps goes up sharply if I wiggle the mouse around while a popup is active. The same behaviour does not occur if there is no popup going. There is an increase in Private Bytes associated with this wiggling, although it's difficult to get a precise handle on how many. Call it, roughly, 150,000 bytes per two second wiggle session.

A G2 collect doesn't collect them, which I'd expect.

Opening and closing a popup with no controls, just a "PopupBackground" Placement, leads to precisely one undisposed bitmap, again with an associated increase in private bytes.

Again, maybe this normal and I'm chasing down the wrong tree (to shamelessly mix metaphors), but it's suspicious enough for me to bring it up here for others to consider. Should I, somehow, be disposing of the "PopupBackgroud" bitmap somewhere?

You'd probably need to post a sample project so I could look into it. Its hard to guess what exactly you're doing.

[Ommina]

I have no idea what they are. Its most likely something .net is using behind the scenes. I cant say I've ever noticed them or any problem steming from their existence.

I won't worry about them then. From my brief bit of reading on them, the appear to be used to make it easier updating the UI from a non-UI thread. So presumably .NET is creating one for each render.

They don't seem to be taking any space -- and at 100K of them an hour, we would notice if they were -- so I'll file them under 'ignore'.

You'd probably need to post a sample project so I could look into it. Its hard to guess what exactly you're doing.

OK, I'm going to take a break from the whole memory management thing for a bit before I turn into a puddle. I'll then see if I can make a The World's Smallest Plugin to go with my World's Smallest Popup, since I'd really appreciate the extra eyes on it.

I'll inflict it on JavaWiz too, since he offered to take a look; a move I'm sure he's going to regret.

But not for a couple days.