GNOME Bugzilla – Bug 579029
soup crashes at home page load
Last modified: 2009-05-05 22:28:25 UTC
Hey. I jumped on to #midori to investigate a crash whenever I loaded up my preferred homepage, http://www.signonsandiego.com. Seemed to not be a Midori problem; the folks on that channel indicated it was a libsoup bug. They were able to consistently reproduce the crash. The page can't finish loading; it gets most of the way done, then crashes the browser. No such issues in Firefox, but Firefox ain't using libsoup. I can't find any special HTML or scripts on that page, except perhaps an embedded flash video (may be realmedia). There is an HTTP meta-refresh on a timed 10-minute interval buried somewhere in the code. Dunno if they're related to soup's failure. I built libsoup with support for SSL, but no other special --enable-foo configure options. Anyway, here's the output: New Thread 0xb40ebb90 (LWP 17391)] [New Thread 0xb3febb90 (LWP 17392)] [New Thread 0xb43ffb90 (LWP 17393)] (midori:17375): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (midori:17375): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `SoupSession' (midori:17375): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)' Program received signal SIGSEGV, Segmentation fault.
+ Trace 214472
Thread 3066398544 (LWP 17375)
Just discovered something interesting: disabling all scripts within Midori, for a completely javascript/whatever-free experience, lets the page load just fine. All other pages work, too. The embedded videos are still perfectly viewable, too. I guess . . . it's a bug in libsoup's script handling?
(In reply to comment #1) > I guess . . . it's a bug in libsoup's script handling? Nope, libsoup doesn't know anything about scripts. It's all just bytes. > #7 0xb7a2897f in soup_message_restarted (msg=0x9e9ad38) at soup-message.c:877 this shows that the crash happens when a message is getting sent a second time. So presumably, when you enable javascript, one of the requests (either a js file itself or else something requested by a script) is getting a redirect response, and for some reason there's a refcounting bug or something that's making libsoup crash when it tries to load the redirected-to resource.
i was able to reproduse this bug with webkit 1.1.5 and it seems fixed with 1.1.6. Seems it was a webkit backend issue. Ticket can be closed.
Yup, webkit-1.1.6 seems to have fixed the error. I dunno where libsoup's interaction fit in, but it all seems okay now. Can load the site with scripts working just fine. My guess is something in webkit was broken that libsoup didn't like, but now webkit's fixed, so libsoup is a happy camper? My take is that this bug can be closed, unless the libsoup folks have other plans.
oops, no, this is a dup of 580193, which got fixed in libsoup. (If you don't have the latest libsoup, then maybe kov put a workaround in WebKit too?) *** This bug has been marked as a duplicate of 580193 ***
hehe. probably thats mine case. I have a -git version of libsoup.
Not really. It may be a side-effect of the new error reporting code, that Jan wrote, though.