|
From: Jan E. <ch...@in...> - 2000-09-26 09:25:44
|
On Tue, 26 Sep 2000, David Clark wrote: >Pete Shinners writes: > > david clark mentioned to me there was a known memory leak in the > > rectangle object stuff i put out recently. i've been attaching the > > new distutils to my little rect object and am pleased with all that. > >My apologies for the misunderstanding. I meant there was a known >memory leak in the pySDL code, not in your rect object. I'm referring >to the leak in the event poll/wait code mentioned in Mr. Kelm's >posting on the 17th. Whoa, so this could be what makes my app eat most of my 256Mb? I had an loop which just polled the event mechanism for new events and just waited for a keypress, and it leaked 5Mb/s. Not too funny. I converted to using wait instead, and now it consumes a lot less memory, but still chews up *a lot*, compared to what the app does (30Mb). Btw, is it my responsibilty to explicitely delete surfaces etc I don't need anymore? I have a few of these, and they are not circularly referenced, so thay should be garbage collected, but my app never seems to release any memory. Thememory usage keeps increasing as I "surf" through my dialogs (I have a *simple* widget library, and create a few fullscreen surfaces). Any idea as to what that could be? I probably do something which can be considered fubar. :-) Chakie --------------------+-------------------------------------------------------- Jan 'Chakie' Ekholm | Balrog New Media http://www.balrog.fi/ Linux Inside | I'm the blue screen of death, nobody hears your screams |