| 2007-05-25 17:05:15 |
Bryce Harrington |
xorg: statusexplanation |
|
Hi, thanks for reporting this problem. Memory leaks can be pretty important symptoms of bugs.
Unfortunately, it's not clear which thing is causing the leak. Can you try the following to see if we can narrow it down:
Disable and turn off beryl, and reboot the computer before bed, and do not load any applications (esp. not firefox). The next day, check memory to see if the leak is still occurring. If so, then it could be xorg or the driver.
Next, do the same but with beryl active.
Finally, do it again but with beryl + firefox.
For whichever case(s) show the leak, please attach:
* The output of 'ps auwx' while it is leaking
* Your /etc/X11/xorg.conf file
* Your /var/log/Xorg.0.log file
Once the cause of the leak is identified, valgrind should be used to investigate the leaks, but let's get through the above first. |
|
| 2007-07-12 23:53:30 |
Bryce Harrington |
xorg: statusexplanation |
Hi, thanks for reporting this problem. Memory leaks can be pretty important symptoms of bugs.
Unfortunately, it's not clear which thing is causing the leak. Can you try the following to see if we can narrow it down:
Disable and turn off beryl, and reboot the computer before bed, and do not load any applications (esp. not firefox). The next day, check memory to see if the leak is still occurring. If so, then it could be xorg or the driver.
Next, do the same but with beryl active.
Finally, do it again but with beryl + firefox.
For whichever case(s) show the leak, please attach:
* The output of 'ps auwx' while it is leaking
* Your /etc/X11/xorg.conf file
* Your /var/log/Xorg.0.log file
Once the cause of the leak is identified, valgrind should be used to investigate the leaks, but let's get through the above first. |
Closing as out of date due to no response from reporter. If the issue persists, please reopen this bug or open a new one, and please include the requested information. |
|
