WebKit Bugzilla
New
Browse
Search+
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
NEW
147882
[GTK] REGRESSION Reproducible segfaults since upgrade of 2.4.8 to 2.4.9
https://bugs.webkit.org/show_bug.cgi?id=147882
Summary
[GTK] REGRESSION Reproducible segfaults since upgrade of 2.4.8 to 2.4.9
nine
Reported
2015-08-11 09:26:44 PDT
We're using the Gtk3::WebKit Perl bindings of WebKitGTK+ in our web application's test suite and since the upgrade to 2.4.9 from 2.4.8 (openSUSE packages) we get reproducible segfaults in pretty much all tests that use WebKitGTK+. The stack traces all look like this: #0 0x00007fffdcc6f932 in WebKit::DOMObjectCache::put(void*, void*) () at /usr/lib64/libwebkitgtk-3.0.so.0 #1 0x00007fffdcd1c147 in webkit_dom_xpath_result_constructor(unsigned long, unsigned int, _GObjectConstructParam*) () at /usr/lib64/libwebkitgtk-3.0.so.0 #2 0x00007fffe25a9bf9 in g_object_new_internal (n_params=0, params=0x0, class=0x1cb7ba80) at gobject.c:1692 #3 0x00007fffe25a9bf9 in g_object_new_internal (class=class@entry=0x1cb7ba80, params=params@entry=0x0, n_params=n_params@entry=0) at gobject.c:1772 #4 0x00007fffe25ab5e1 in g_object_newv (object_type=object_type@entry=391362448, n_parameters=n_parameters@entry=0, parameters=parameters@entry=0x0) at gobject.c:1921 #5 0x00007fffe280917e in XS_Glib__Object_new (my_perl=<optimized out>, cv=0x15d9e548) at GObject.xs:1379 #6 0x00000000004b590b in Perl_pp_entersub (my_perl=0x7a8010) at pp_hot.c:2794 #7 0x00000000004ae406 in Perl_runops_standard (my_perl=0x7a8010) at run.c:42 #8 0x0000000000440c8d in perl_run (oldscope=<optimized out>, my_perl=<optimized out>) at perl.c:2451 #9 0x0000000000440c8d in perl_run (my_perl=0x7a8010) at perl.c:2372 #10 0x000000000041ee23 in main (argc=3, argv=0x7fffffffd7a8, env=0x7fffffffd7c8) at perlmain.c:114 Please tell me, how I can help solve this.
Attachments
Add attachment
proposed patch, testcase, etc.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug