You can do a similar exercise to see if memory goes low:
while sleep 60; do free|grep buffers/cache >> /tmp/free.log ; done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1007257
Title:
glschool, an
On Sat, July 7, 2012 5:48 am, Tormod Volden wrote:
> So there does not seem to be a bug in glschool then?
>From what has been said, it seems to be the kernel module. This is the
only use I have for GL graphics and so it seemed associated with the
screen saver. The screen save cycles (restarts freq
So there does not seem to be a bug in glschool then?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1007257
Title:
glschool, and maybe others has memory leak
To manage notifications about this bug g
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1007257/+attachment/3174471/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1007257
Ti
Looks like I was wrong. It looks like it restarts every 10 minutes. The
only upward number I see is the pid. It does look like the memory use
goes up and stays there when the screen saver goes off.
** Attachment added: "glschool-ps.log"
https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+b
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1007257/+attachment/3174470/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1007257
Title:
gls
Thanks for clearing that up. If the used memory is reclaimed afterwards, it is
not a kernel driver problem. I would then rather suspect the mesa libraries.
Are you able to log in remotely from another computer and run "ps aux" while
the screensaver is running?
Otherwise please set up the screen
I didn't think I said that memory was consumed after the screen saver
has stopped. Just that the amount of swap used showed that something had
been pushed there at some time. The only thing different between two
runs was the screen saver. With the screen saver turned off over 12
hours top shows abo
Thanks for your report. The fact that the memory is consumed also after
the screensaver has stopped, indicates that the kernel is leaking the
memory. I assume "top" does not show any memory hogs? There have been
some issues with for instance the intel graphics kernel driver leaking
memory objects.
** Description changed:
With screen saver set to "Blank Screen Only", swappiness 0 and the
system left running over night, swap shows 0 usage the next day as I
- would expect. However, if I set screen saver to glschool, swappiness 0
- and system run over night, my swap space is about half full
10 matches
Mail list logo
