On Tue, 2007-10-16 at 05:54 +0000, Danny Baumann wrote: > Although I'm obviously biased (as the one who wrote ring), I have to say that > I really, really doubt there is a leak that may fill several hundred > megabytes of memory inside ring. > Besides the usual boilerplate code that every compiz plugin has, there is > only one place of allocation where a 8 byte structure is allocated for each > window in the ring. So even if it wasn't freed correctly (which it is here), > it would take ages to fill up memory with that allocation, unless you have a > really absurd amount of windows in the ring. > The second place where stuff is allocated from ring is the window title > display (which is also freed just fine here) ... if you want to check that, > just disable either the window title display or the text plugin. > > For me, the issue sounds like a driver problem, just as sampsa wrote > before me. > i unfortunately seem to have spoken too soon. after about 15 hours with the ring disabled, my usage is creeping up, from around 20M now up to 75M, and I expect it will continue to rise. sorry about that. the creep was much much faster when ring *was* enabled, but maybe my usage pattern was different as well.
matt -- Matt Price [EMAIL PROTECTED] -- memory leak with ring https://bugs.launchpad.net/bugs/151168 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
