Original reporter indicates issue was a client app and is now resolved; closing as fixed.
To other commenters on this bug, X memory use is primarily a function of what client apps request; if a client app has a bug and mismanages its X memory, it shows up as increased xserver memory load. But the bug is still in the client app. It's a similar situation with high CPU usage... see https://wiki.ubuntu.com/X/Troubleshooting/HighCPU for some extra notes. Sometimes you can determine what clients are consuming excess memory using the xrestop command, depending on the type of X memory the client is consuming. Anyway, >90% of the time when X has high cpu or memory, you should assume a *client* problem, not a leak in xorg itself. ** Changed in: xorg (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/763370 Title: xorg memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/763370/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
