Petar Volkovski, What you did in comment #51 is just another variation of the testcase in the bug description that others have been performing (and that you insist does not represent a memory leak).
Your output differs from mine in that the GEM allocation increases *and* decreases. I have never seen the GEM object bytes allocation decrease on my system (as I said, even when I close every application and leave nothing but an empty GNOME desktop and panel running); only stopping/restarting the server will reduce the allocation. I can understand that the object bytes may level out at a certain size, but on my system it grows out of control. Once it hits ~300MB (of a system with the integrated graphics set to 128MB, and with just 768MB ram in total), the system becomes unusable due to I/O and swapping. It is clearly a memory leak. -- [KMS] gem objects not deallocated https://bugs.launchpad.net/bugs/565981 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
