Nominated precise. Though I know it's unlikely to get a fix any time
soon, unless someone can identify the change between Mesa 8.0 and 9.0
that (apparently) fixed the bug.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
Hi folks,
I'm still regularly stricken by the memory leak in the compiz process.
I have to kill compiz every couple of days after it bloats to several GB
in size. From reading this bug, it's not clear to me what has been
fixed, where any possible fix is destined to, how I could pick it up, or
This appears to have been fixed in Mesa some time by 12.10. Last time I
could reproduce it was in oneiric (Mesa 7.11) but can't reproduce it now
in quantal (Mesa 9.0). Given the comments on this bug kind of stopped
around April, it could be that the fix was released in Ubuntu 12.04 with
Mesa
Duplicate bug 998708 suggests this was still a problem on precise in
Mesa 8.0.2 at least.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/914773
Title:
[radeon] Compiz memory leak and blank
** Changed in: compiz
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/914773
Title:
[radeon] Compiz memory leak and blank screen unable to login when
** Changed in: compiz
Assignee: (unassigned) = Daniel van Vugt (vanvugt)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/914773
Title:
[radeon] Compiz memory leak and blank screen unable to
** Changed in: compiz/0.9.8
Milestone: 0.9.8.6 = 0.9.8.8
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/914773
Title:
[radeon] Compiz memory leak and blank screen unable to login when
** Changed in: compiz-core
Milestone: 0.9.7.10 = 0.9.7.12
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/914773
Title:
[radeon] Compiz memory leak and blank screen unable to login when
** Changed in: compiz
Status: Confirmed = Fix Released
** Changed in: compiz/0.9.8
Status: Confirmed = Fix Released
** Changed in: compiz-core
Status: Confirmed = Fix Released
** Changed in: compiz (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: mesa
** Changed in: compiz
Status: Fix Released = Confirmed
** Changed in: compiz
Assignee: artur bryczek (arturbryczek) = (unassigned)
** Changed in: compiz/0.9.8
Status: Fix Released = Confirmed
** Changed in: compiz/0.9.8
Assignee: artur bryczek (arturbryczek) =
** Changed in: compiz
Milestone: 0.9.8.4 = 0.9.9.0
** Also affects: compiz/0.9.8
Importance: Undecided
Status: New
** Changed in: compiz/0.9.8
Status: New = Confirmed
** Changed in: compiz/0.9.8
Importance: Undecided = Critical
** Changed in: compiz/0.9.8
Milestone:
** Changed in: compiz
Milestone: 0.9.8.2 = 0.9.8.4
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/914773
Title:
[radeon] Compiz memory leak and blank screen unable to login when
using
** Changed in: compiz
Assignee: Daniel van Vugt (vanvugt) = (unassigned)
** Changed in: compiz-core
Assignee: Daniel van Vugt (vanvugt) = (unassigned)
** Changed in: mesa (Ubuntu)
Importance: Undecided = Critical
--
You received this bug notification because you are a member of
** Changed in: compiz
Milestone: 0.9.8.0 = 0.9.8.1
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/914773
Title:
[radeon] Compiz memory leak and blank screen unable to login when
using
Just a note that
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI
RV516 [Radeon X1300/X1550 Series]
also triggers this so it is not specific to R600+ drivers.
For these old GPUs FGLRX is not available so there is no workaround...
--
You received this bug notification
** Changed in: compiz
Milestone: None = 0.9.8.0
** Changed in: compiz-core
Milestone: 0.9.8.0 = None
** No longer affects: compiz-core/0.9.7
** Changed in: compiz-core
Milestone: None = 0.9.7.10
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Changed in: compiz
Importance: Undecided = Critical
** Changed in: compiz
Status: New = Confirmed
** Changed in: compiz
Assignee: (unassigned) = Daniel van Vugt (vanvugt)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa
** Description changed:
The issue appears to be that radeon's implementation of
glXWaitVideoSyncSGI (from libgl1-mesa-glx) hangs and leaks X events
while the screen is locked and asleep. The leak is around 200 bytes (one
XEvent) per frame or about 12.5KB per second.
It is most
** Changed in: compiz (Ubuntu)
Status: Invalid = Confirmed
** Project changed: indicator-multiload = compiz-core
** Changed in: compiz-core
Status: Invalid = Confirmed
** Changed in: compiz-core
Milestone: None = 0.9.8.0
** No longer affects: unity (Ubuntu)
** Changed in:
Using the fglrx driver solves the bug.
But I'm still not sure about Sync to VBlank solving it, because it
seems memory usage does go up again. How can I check if compiz really is
not syncing to VBlank?
--
You received this bug notification because you are a member of Ubuntu-X,
which is
I confirmed the bug with radeon today. It leaked some gigabytes fairly
quickly. Couldn't reproduce any such leak with intel graphics under the
same conditions.
Though, the leak only happened with radeon if I left some program running that
continuously redraws while the screen is locked and in
** Description changed:
- The issue *appears* to be that radeon's implementation of
+ The issue appears to be that radeon's implementation of
glXWaitVideoSyncSGI (from libgl1-mesa-glx) hangs and leaks X events
- while the screen is locked or asleep.
+ while the screen is locked and asleep. The
a new bug report maybe?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/914773
Title:
[radeon] Compiz memory leak and blank screen unable to login when
using radeon driver
To manage
No need for new bug reports. There's only one topic here.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/914773
Title:
[radeon] Compiz memory leak and blank screen unable to login when
using
I double checked and turning Sync to VBlank off does solve the leak. I
will check again tonight with Sync to VBlank enabled and every program
that redraws minimised or shut down.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
Hmm, oops, 5% is 200MB, or even 400MB if I should include swap, don't
know what went wrong there.
This weekend I left my pc idle for more than 24 hours, when I checked
via ssh after 20 hours it was up to the usual 12% (the percentage I
always see after 8+% hours of being idle. But when I tried to
The previous valgrind output showed the primary leak originated from
waitForVideoSync. If it's still leaking with Sync To VBlank disabled
then you must have a leak originating somewhere else. Please provide
valgrind leak details from with Sync To VBlank disabled.
Also, please try the fglrx
** Description changed:
+ The issue *appears* to be that radeon's implementation of
+ glXWaitVideoSyncSGI (from libgl1-mesa-glx) hangs and leaks X events
+ while the screen is locked or asleep.
+
WORKAROUNDS:
-
Try each of these, individually and together:
1. Before leaving/locking the
Actually, the primary leak in _XEnq is going to happen to any OpenGL
app, not just compiz. And the secondary leak in
PrivateScreen::processEvents() is caused completely by the primary leak.
So this is not a compiz-specific issue. It's just that compiz is usually
the only OpenGL program that most
It's still not clear which Mesa/DRM/radeon packages this bug should be
assigned to. But it's some combination thereof.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/914773
Title:
[radeon]
Memory usage of compiz was up to 5% (100MB) again with VSync disabled
and not using pc for 3 hours, didn't restart compiz though, don't know
if that is necessary when changing that option.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in
Sounds like better news if the PC was still usable, but the 100MB is
still not great. It is however a much lower rate of leakage per hour
than before.
I would be interested to see what valgrind (or massif) reports as the
source of the leaks (or bloat) when vsync is disabled.
Please also try the
I don't think turning off the monitor will necessarily be a viable
workaround. It may in fact trigger this bug also.
** Description changed:
+ WORKAROUNDS:
+
+ Try each of these, individually and together:
+
+ 1. Before leaving/locking the PC run ccsm, and in the OpenGL section
+ disable Sync
33 matches
Mail list logo
