Created attachment 41051 [details] backtrace I just upgraded to 1.1.15.2 with liferea-1.7.1. Liferea's UI maps, but it crashes when I select a message to read. The liferea folks say this is a webkit issue. I've attached the output of 'liferea --debug-all' which contains a backtrace at the end.
Are you able to provide a reduction that can trigger the crash?
Unfortunately, I'm neither a developer of Liferea or webkit and so can't really help you. On the other hand, I've built everything with debugging symbols (-O2 -g for gcc's c[xx]flags) and so can easily set up any traces you can think of. Just let me know where to set the breakpoints. Also, the crash occurs as soon as I try to view any message that liferea brings down.
(In reply to comment #2) > Unfortunately, I'm neither a developer of Liferea or webkit and so can't really > help you. On the other hand, I've built everything with debugging symbols (-O2 > -g for gcc's c[xx]flags) and so can easily set up any traces you can think of. > Just let me know where to set the breakpoints. > > Also, the crash occurs as soon as I try to view any message that liferea brings > down. Can you get an actual debug build (--enable-debug) and send a new trace? It's not trivial to know what's going on otherwise. Also, mixing -O2 and -g flags is not the best idea in general.
Created attachment 41292 [details] gdb trace of SIGSEGV I build all of gnome and friends with debugging support (albeit with -O2).
Created attachment 41681 [details] GDB Backtrace for liferea using libwebkitgkt+ version 1.1.15.3 I upgraded to today's release of webkitgtk+. Configured with --enable-debug as requested and rebuilt. The problem is still here. The attached trace should be useful.
(In reply to comment #5) > Created an attachment (id=41681) [details] > GDB Backtrace for liferea using libwebkitgkt+ version 1.1.15.3 > > I upgraded to today's release of webkitgtk+. Configured with --enable-debug as > requested and rebuilt. The problem is still here. The attached trace should > be useful. Thanks. Turns out we are missing an important fix in our stable branch, so this will be fixed in 1.1.15.4, which we'll release ASAP. I'll close this bug when that happens.
If 1.1.15.4 isn't going to be released today could you point me to a file containing the relevant patch?
I just built and installed 1.1.16. The problem seems to have been fixed. Thanks!
(In reply to comment #8) > I just built and installed 1.1.16. The problem seems to have been fixed. > > Thanks! Closing bug.