Thanks for your attention Pedro.
I've attached the Valgrind log from running gimp like so:
$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v
--tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind-
gimp.log gimp
During the session, I opened GIMP, let it sit there for a few minutes
(got called away from the computer), then opened the file menu. After
that, it crashed.
Right off the bat, I noticed some pango-graphite stuff on one of the
stacks. It turns out that I had also been getting crashes from gnome-
volume-control after I submitted this issue about gimp. I ran it under
Valgrind and noticed the same pango-graphite stuff.
Since pango-graphite is a universe package, I'm not sure how you guys
treat this exactly (I'm very new to Ubuntu). I figured I'd still provide
the Valgrind log either for posterity or in case anyone's interested in
figuring out the cause of the bad interaction.
** Attachment added: "Valgrind log"
http://launchpadlibrarian.net/38292229/valgrind-gimp.log.gz
--
gimp-2.6 crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/509212
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
