Bug#712815: Memory Leak

[Robin]

Used all ram first run crashing valgrind, approx 85 min
Second run, stopped at 50%ram dump file attached below
Bug reported for info only as I can shut gnome-mahjongg down after finished
playing.

rob



On 21 June 2013 22:36, Emilio Pozuelo Monfort <pochu at debian.org> wrote:

> On 19/06/13 19:49, Robin wrote:
> > Package: mahjongg
> > Version: 1:3.8.0-1
> >
> > Please note attempted reporting with reportbug and reportbug-ng but bug
> did not
> > register with bugs.debian.org, so reporting manually
> >
> >
> > start game and leave running, process consumes increasing amounts of
> memory.
> >
> > Ran twice with valgrind:
> >
> >  run 1:
> >
> > rob at localhost:~$ valgrind gnome-mahjongg
> > ==12456== Memcheck, a memory error detector
> > ==12456== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
> > ==12456== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright
> info
> > ==12456== Command: gnome-mahjongg
> > ==12456==
> > ==12456==
> > ==12456== HEAP SUMMARY:
> > ==12456==     in use at exit: 2,063,512,405 bytes in 90,405 blocks
> > ==12456==   total heap usage: 3,132,843 allocs, 3,042,438 frees,
> 4,198,594,738 b
> > ytes allocated
> > ==12456==
> > ==12456== LEAK SUMMARY:
> > ==12456==    definitely lost: 2,916,848 bytes in 3,880 blocks
> >            possibly lost: 124,082,557 bytes in 5,574 blocks
> >
> >
> > run2:
> >
> > ==14190== LEAK SUMMARY:
> > ==14190==    definitely lost: 581,680 bytes in 775 blocks
> > ==14190==    indirectly lost: 377,856,168 bytes in 15,028 blocks
> > ==14190==      possibly lost: 31,233,257 bytes in 4,276 blocks
> > ==14190==    still reachable: 2,044,297 bytes in 9,115 blocks
> > ==14190==         suppressed: 0 bytes in 0 blocks
> > ==14190== Reachable blocks (those to which a pointer was found) are not
> shown.
> > ==14190== To see them, rerun with: --leak-check=full --show-reachable=yes
> > ==14190==
> > ==14190== ERROR SUMMARY: 1445 errors from 1445 contexts (suppressed: 2
> from 2)
> > --14190--
> > --14190-- used_suppression:      2 dl-hack3-cond-1
> > ==14190==
> > ==14190== ERROR SUMMARY: 1445 errors from 1445 contexts (suppressed: 2
> from 2)
> >
> > Watching process on htop after approx 15 mins res mem has increased
> > from c.18224 B to 573MB
>
> These logs have a summary but no traces. You would need to run valgrind
> with
>
> G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind --tool=memcheck
> --leak-check=full --leak-resolution=high --num-callers=20
> --log-file=vgdump mahjongg
>
> And then attach the vgdump file.
>
> It's unlikely that we will fix any non-major leaks in non-critical apps in
> a
> stable release though, as one usually doesn't leave mahjongg running for
> days.
> Usually.
>
> Emilio
>



-- 
*rob
*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20130622/59560514/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: vgdump
Type: application/octet-stream
Size: 2333591 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20130622/59560514/attachment-0003.obj>