Re: gnome-shell got memory leaks ?





On Sat, Jun 23, 2012 at 2:35 PM, Jasper St. Pierre <jstpierre mecheye net> wrote:
On Sat, Jun 23, 2012 at 2:20 AM, 邓尧 <torshie gmail com> wrote:
>
>
> On Thu, Jun 21, 2012 at 12:44 AM, Jasper St. Pierre <jstpierre mecheye net>
> wrote:
>>
>> On Wed, Jun 20, 2012 at 11:59 AM, Bijan Binaee <bijanbina gmail com>
>> wrote:
>> > i run gnome shell in valgrind and it show that gnome-shell have about
>> > 3500
>> > memory error!!!
>> > and leak about 10 MB!!!
>> > also i note that i just ran it and i haven’t opened any window and close
>> > it
>> > and maybe if i do that you see a lot more problem
>> >
>> > here is valgrind log:http://paste.kde.org/504602/
>> > also because my gnome-shell is not compiled with debug flag backtrace is
>> > not
>> > available perfectly
>>
>> Yes. We need debug symbols.
>>
>> You need to run with --leak-check=full. Also, G_SLICE=always-malloc and
>> G_DEBUG.
>>
>> See http://live.gnome.org/Valgrind
>>
>> Also, using a suppressions file like the one provided with Clutter is
>> always a good idea.
>>
> I also tried gnome-shell under valgrind. gnome-shell was started with
> "valgrind --leak-check=full --show-reachable=yes --log-file=gnome-shell.log
> gnome-shell --replace", then stopped with command "gnome-shell --replace".
> The valgrind log can be downloaded here:
> http://www.xiahaiqu.com/gnome-shell.log.gz
> According to the valgrind log, both nvidia driver (/usr/lib/libGL.so) and
> gnome-shell got leaks. Not all debug symbol files are installed, if more
> debug symbols are need, let me know.
>
> btw, when starting gnome-shell I got the following console error message,
> not sure whether it's important or not.
> (gnome-shell:7493): folks-WARNING **: Failed to find primary PersonaStore
> with type ID 'eds' and ID 'system'.
> Individuals will not be linked properly and creating new links between
> Personas will not work.
> The configured primary PersonaStore's backend may not be installed. If you
> are unsure, check with your distribution.
>
> Thanks
> Yao
>

It does not seem like you set the correct environment variables, as I
can still see random things caused by valgrind not understanding the
slab allocator. Additionally, please try and use a suppressions file.
I recommend the one in Clutter's tree:

   http://git.gnome.org/browse/clutter/plain/tests/data/clutter-1.0.suppressions

--
  Jasper
 
OK, tried with G_DEBUG & G_SLICE set,

G_DEBUG=gc-friendly G_SLICE=always-malloc valgrind --leak-check=full --show-reachable=yes --log-file=3.log --suppressions=clutter-1.0.suppressions gnome-shell --replace

The log is here: www.xiahaiqu.com/3.log.gz Still got lots of leaks, but most of them originated from libmozjs and libGL. Leaks originated from libGL not necessarily means bugs in nvidia driver, might be incorrect use of opengl.

Thanks
Yao



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]