Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#1076 Crash when closing internal browser

v1.10
closed
nobody
None
7
2014-12-15
2013-05-04
No

Sometimes Liferea (current[*] Git version) crashes for me when an internal browser window is closed. It doesn't seem to happen on every feed, just some, and not every time.

Steps to reproduce:
1. Add feed http://haggstrom.blogspot.com/feeds/posts/default - an example of a feed where this bug appears.
2. Click on a headline in the itemlist.
3. Middle-click on the title to open internal browser in a new tab
4. Go to the newly opened tab.
5. Close the tab.
6. Crash. If not, repeat steps 3-5. I've found it often happens after a second open/close.

Liferea gives the following output on crash:

(liferea:2651): Gdk-ERROR **: The program 'liferea' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
  (Details: serial 8321 error_code 9 request_code 62 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap (core dumped)

I'll see if I can generate a backtrace per instructions.

  • commit 6ac425191e07049cbd555dfafeb08d772d2c5f58

Discussion

  • Ok, here we go. I installed the debug packages for x11-6, libwebkitgtk-3.0.0, libglib2.0.0, libgtk3-0 and libcairo-2 and issued:

    GDK_SYNCHRONIZE=yes gdb ./src/liferea
    

    After doing run it takes several minutes to start! I guess because of the huge libwebkitgtk debug symbol package..?

    Anyway, backtrace is attached. Hope it helps. Say if you need anything more.

     
  • Through guidance from Lars on IRC, I discovered that this bug also appears in Epiphany and is therefore clearly a webkitgtk bug. I've reported it to Ubuntu:

    https://bugs.launchpad.net/ubuntu/+source/webkit/+bug/1176487

    This bug can thus be closed, which I would now do, but I just can't figure out how! I see no link to edit the ticket.

     
  • Adrian Bunk
    Adrian Bunk
    2013-05-05

    • status: open --> closed