Hi, on my hardy 64bit, I get this very strange set of memory consumption values for some processes. For some others its looks fine (I am not sure anymore if those values are correct anyway). Attaching a screenshot. Has anyone seen a process in their system monitor that takes up 17179869180.0 GB RAM ??
Ubuntu User #21703 Linux User #470446 HP 6710b, C2D T7300 2GB RAM Intel X3100 Graphics | lucid lynx 64b Core2Quad Q6600 6GB | 12.04 64b http://tech.sraghav.in
i have had a similar problem with this, but instead, it says that i was using 100 percent of my cpu. it must be a bug, especially when i have equipment capable of running linux, its an amd 3000+
The "insane memory usage" problem is an Xgl bug. The sooner we can drop that unmaintained annoyance, the better. If system monitor says CPU utilisation is at 100%, it's likely correct.
Remember: if your problem is not described on a Launchpad bug, it can only be fixed by accident!
Originally Posted by RAOF The "insane memory usage" problem is an Xgl bug. The sooner we can drop that unmaintained annoyance, the better. If system monitor says CPU utilisation is at 100%, it's likely correct. Well, for me its says 50% CPU, but I guess that would be because I am on Core2Duo, and system monitor shows 2 cpus in there. So, effectively its hogging 1 cpu 100% resulting in effectively 50% usage overall. How about a bug reported on this issue ? Is it already reported ?
Instead of using the graphical system monitor, use the command line based htop Code: sudo apt-get install htop There is a bug in system monitor itself. Running htop on command line yields accurate reading of your system.
sudo apt-get install htop
Last edited by retrow; May 6th, 2008 at 06:25 AM.
Face your daemons
Originally Posted by s_raghu20 Well, for me its says 50% CPU, but I guess that would be because I am on Core2Duo, and system monitor shows 2 cpus in there. So, effectively its hogging 1 cpu 100% resulting in effectively 50% usage overall. How about a bug reported on this issue ? Is it already reported ? What issue? What program is taking 100% of a core for you? This can be entirely normal if, for example, that program is doing something fundamentally CPU intensive .
Originally Posted by RAOF What issue? What program is taking 100% of a core for you? This can be entirely normal if, for example, that program is doing something fundamentally CPU intensive . The point was about system monitor showing insanely huge memory consumption values for processes. The CPU usage that I reported was for gnome-display-properties thing. I think I confused between two threads and mentioned my cpu usage stats here, whereas they were meant to be taken in the view of this thread - http://ubuntuforums.org/showthread.php?t=783619 So, back to the system monitor thing, how is it supposed to be fixed then ? The fact that it reports wrong values for memory used remains. Has it been raised as a bug ? Is there some update/fix already available ? Or is it just because I am using xserver-xgl ?
You can report the bug at Launchpad. If it has already been reported, you will be directed to the thread where people are discussing/debugging the cause and nature of this bug while working on a fix at the same time.
It's already been reported here: https://bugs.edge.launchpad.net/ubun...gl/+bug/148325. A good workaround is generally to remove or disable[1] Xgl - almost everyone doesn't need it . [1] To disable Xgl, create a file called 'disable' in ~/.config/xserver-xgl
Last edited by RAOF; May 6th, 2008 at 08:02 AM.
Originally Posted by RAOF It's already been reported here: https://bugs.edge.launchpad.net/ubun...gl/+bug/148325. A good workaround is generally to remove or disable[1] Xgl - almost everyone doesn't need it . [1] To disable Xgl, create a file called 'disable' in ~/.config/xserver-xgl Thanks for the pointer. Though I dont mean to be critical, but the overall situation about this bug looks strange. On Gnome, its marked as RESOLVED, and still we are facing it in latest gnome build in hardy. There it says in Resolution tag as NOTGNOME, which I interpret as gnome team deciding that its not a gnome bug. anybody knows where to track it further ? who develops/maintains that package ?
Ubuntu Forums Code of Conduct