" So while the monitor is inactive, unhandled events queue up in the
compiz process. And it would appear even after the monitor wakes, the
backlog of 1.5 million events is too large. So compiz appears to hang,
or never catches up. "
When I become active again after a long period of inactivity, and
A third workaround that might work would be to try AMD's fglrx ATI
driver. You will lose KMS, but it's probably worth testing for a little
while, just to confirm this bug.
** Summary changed:
- Compiz memory leak and blank screen unable to login
+ [radeon] Compiz memory leak and blank screen unab
Thanks. Please try the two workarounds I suggested:
1. Disable "Sync To VBlank"; or
2. Minimize windows that are redrawing lots (like a browser or VM).
You only need to do either before locking/leaving your PC for several
hours.
--
You received this bug notification because you are a member of
** Attachment added: "ccsm_settings.profile.bz2"
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/914773/+attachment/2804614/+files/ccsm_settings.profile.bz2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
** Attachment added: "dmesg.bz2"
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/914773/+attachment/2804613/+files/dmesg.bz2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914773
Title:
Com
It's an onboard Radeon HD3200 using the radeon driver (with KMS) on a
20" Dell 2007WFP monitor.
Attached dmesg.log, Xorg.0.log and my current ccsm config.
** Attachment added: "Xorg.0.log.bz2"
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/914773/+attachment/2804612/+files/Xorg.0.log.
In fact, the number 1,500,000 makes sense. That's probably the number of
video frames (monitor refresh rate) that your system would normally
render in 8 hours.
However, compiz won't try to render a new frame unless some part of the
screen is changing. So maybe another simple workaround is to minim
A workaround to avoid this problem should be:
Run ccsm, and in the OpenGL section disable "Sync To VBlank".
If you do this just before leaving your computer for the night (and
assuming my theory is right), then that should avoid the bug.
--
You received this bug notification because you are a me
Thanks kayandus, that valgrind output is intriguing.
It would appear the two leaks are the result of a blockage in compiz
event loop. I am guessing that after many hours, maybe your monitor has
gone to sleep. And that is causing PrivateGLScreen::waitForVideoSync to
hang inside either glXGetVideoSy
Attached the full valgrind log, while running compiz for about 8 hours,
with options --leak-check=full --show-reachable=yes enabled. Most
interesting part is probably the last few lines of the log:
==17463== 314,222,480 bytes in 1,510,685 blocks are still reachable in loss
record 7,754 of 7,755
=
Oh and not using unity either, just plain compiz.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914773
Title:
Compiz memory leak and blank screen unable to login
To manage notifications about this
I'm also affected by this bug. If I'm not using my PC for I think around
10 hours, there's like a 50% chance compiz has used up almost all
memory. Only thing you can do is go to the console and SIGKILL it (won't
listen to SIGTERM). Also on 64-bit and NOT running indicator-multiload.
--
You receiv
** Project changed: compiz => compiz-core
** Changed in: compiz-core
Status: New => Incomplete
** Changed in: compiz-core
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
As I understand the bug report, the memory leak is in compiz?
Closing as invalid for indicator-multiload.
** Changed in: indicator-multiload
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
I ran the 64 bit one for a significant time without any of these errors.
My guess is that this is a leak in indicator-multiload as that is the
only difference we had.
** Project changed: unity => indicator-multiload
** Changed in: indicator-multiload
Milestone: 4.30.0 => None
--
You receiv
I have tested, and this bug is isolated to x86-64 architecture. Another
words, this bug is non existant in 32 bit systems. Anyone know why?
When I tested on x86-64, I was using indicator-multiload = lets hope the
fix gets sponsored soon.
--
You received this bug notification because you are a me
Are you using indicator-multiload? There was a fix made to nux that may
fix this issue or related one. I have backported the fix for oneiric and
waiting for it to get sponsored. so the update may soon reach oneiric
users as well, see bug 888039
--
You received this bug notification because you ar
I got the leak again. I was only away from the machine for 8 hours.
I was able to switch to VT1 and kill firefox and skype, which freed
enough memory that the login prompt would come up, and I was able to
login.
Compiz has been running since 22 Jan and is now up at 3.5 gig (I have
stopped by kvm
When I arrived into work this morning I couldn't unlock the computer, I
was just getting blank screens. A switch to VT1 and running top (both of
which were awfully slow) revealed that compiz was using 12G of memory,
so there is definitely a rather bad leak somewhere.
--
You received this bug noti
I've also had memory leaks in the past, but none as massive as this one.
That could well be because I never left my computer on for that much
time.
** Changed in: unity
Status: New => Triaged
** Changed in: unity (Ubuntu)
Status: New => Triaged
** Changed in: unity (Ubuntu)
Im
I have had this problem a number of times in the past, it normally
occurs if my machine is left running for a few days whilst I am away, so
an hours log probably does not have this issue, but there are certainly
a few memory leaks in the current version (or its libraries).
--
You received this bu
Attached is valgrind.log
==15020== LEAK SUMMARY:
==15020==definitely lost: 71,205 bytes in 1,101 blocks
==15020==indirectly lost: 303,006 bytes in 4,119 blocks
==15020== possibly lost: 39,590 bytes in 470 blocks
==15020==still reachable: 6,922,482 bytes in 41,776 blocks
==15020==
Added in symbol packages and ran compiz for a couple of minutes under
valgrind.
==14236== LEAK SUMMARY:
==14236==definitely lost: 57,142 bytes in 707 blocks
==14236==indirectly lost: 121,649 bytes in 3,809 blocks
==14236== possibly lost: 505,138 bytes in 2,110 blocks
==14236==stil
Compiz used up the memory whilst I was away from the computer for a
couple of days after restarting lightdm it went back down to 626meg,
from about 8gig prior to creating the bug report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914773
Title:
Compiz memory leak and blank screen unable to login
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sourc
25 matches
Mail list logo
