Reopening, that doesn't crash with that host extra lines on my box, the bug looks like a memory corruption, nothing obvious to the valgrind log though. Could you try to get an another valgrind log with "G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind..."?
Reopening, that doesn't crash with that host extra lines on my box, the bug looks like a memory corruption, nothing obvious to the valgrind log though. Could you try to get an another valgrind log with "G_SLICE= always- malloc G_DEBUG=gc-friendly valgrind..."?