Ah, thanks for that! Patch applied. For the other memory leaks, the best way to look into them is to do a metacity --replace. This is the only way you can tear down all the compiz stuff at runtime and should give you a better view of what's going on.
On Mon, Apr 11, 2011 at 8:43 AM, Abhishek Udupa <[email protected]> wrote: > I've narrowed it down to the PrivateScreen::syncStacks () function in > src/screen.cpp. There's a call to XQueryTree there and the "children" > variable which XQueryTree returns does not look like it escapes the > function, nor is it freed. I've attached a patch that fixes it for me (2 > hours of uptime with compiz memory usage steady at 21 MB). > > I'm no compiz developer nor am I an X11 hacker, so I'm not sure of this > is the right fix. Could the compiz package maintainers please validate > the fix as well as pull in the patch? > > ** Patch added: "Patch for the Compiz memory leak" > > https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/755863/+attachment/2013293/+files/compiz.patch > > -- > You received this bug notification because you are a member of compiz > packagers, which is subscribed to compiz in Ubuntu. > https://bugs.launchpad.net/bugs/755863 > > Title: > Compiz uses increasingly large amounts of memory > > _______________________________________________ > Mailing list: https://launchpad.net/~compiz > Post to : [email protected] > Unsubscribe : https://launchpad.net/~compiz > More help : https://help.launchpad.net/ListHelp > -- Sam Spilsbury -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/755863 Title: Compiz uses increasingly large amounts of memory -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
