Control: tags -1 + moreinfo On Tue, Feb 28, 2017 at 03:31:41PM +0200, Andres Gomez wrote: > Package: libglib2.0-0 > > my locally built epiphany SIGSEVed in slab_allocator_free_chunk, after > visiting several pages.
On Tue, Feb 28, 2017 at 05:41:02PM +0200, Andres Gomez wrote: > Package: libgtk-3-0 > > My locally built epiphany SIGSEVed in gtk_css_static_style_new_compute, after > visiting several pages. Both of these are more likely to be a bug in webkit or epiphany than in glib or gtk. For a next step, try setting the environment variable G_SLICE=debug-blocks before running and see if you can get an abort() closer to your bug. If that doesn't work and you're feeling adventurous, you can try some other things like compiling with AddressSanitizer (-fsanitize) or running under valgrind. The problem with memory corruption bugs is that the stack trace you've provided only shows where the memory corruption was detected. It doesn't show where the memory corruption actually happened.
