I ran g-s-d through valgrind for 2 days now, and the issues seems to have happened twice during the night, which is consistent with what I though was my experience without valgrind as well. May have something to do with turning off or locking the screen when the laptop is not in use - there is nothing else happening over night that I know of.
I piped the command through tee in order to also catch g-s-d's own debug log: G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log gnome- settings-daemon debug | tee gnome-settings-daemon-with-valgrind- debug.log Both log files are attached ** Attachment added: "valgrind.log" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/410534/+attachment/3340539/+files/valgrind.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/410534 Title: gnome-settings-daemon crashed with SIGSEGV in g_slice_alloc() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/410534/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
