I'm trying to catch that function(s) which leaks the memory, but
unfortunately I am not an expert. Can anyone help me what to do? I
copied /usr/bin/gnome-shell to /usr/bin/gnome-shell.bin and made a
script in /usr/bin/gnome-shell:

#!/bin/sh
if [ $USER = gstest ] ; then exec valgrind --tool=massif --num-callers=500 
--massif-out-file=/tmp/massif.out.%p 
--log-file=/tmp/gnome-shell.valgrind.log.%p $0.bin $* ; fi
exec $0.bin $*

after that I logged in as gstest and watched the valgrind output with
massif-visualizer. But I don't know how to control the frequency of
writing out the massif.out.pid file? This file was wrote out couple
minutes after logging in, but after that nothing was written out for
hours. It would be better to see continuously what is happening when I
e.g. push Super+A.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850201

Title:
  Memory usage grows when locking/unlocking the screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850201/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to