Bug 56834

Summary: [GTK] Moving back in history causes segfault
Product: WebKit Reporter: Priit Laes (IRC: plaes) <plaes>
Component: WebKitGTKAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: kevin.cs.oh, mrobinson, xan.lopez
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: PC   
OS: Linux   

Priit Laes (IRC: plaes)
Reported 2011-03-22 08:15:19 PDT
epiphany-2.91.92 webkit-gtk-1.3.13 Rapidly clicking on link and then moving back in history (right click menu -> back) causes segfault quite often: Program received signal SIGSEGV, Segmentation fault. g_type_check_instance_is_a (type_instance=0x363bea0, iface_type=<value optimized out>) at gtype.c:3961 3961 gtype.c: No such file or directory. in gtype.c (gdb) bt #0 g_type_check_instance_is_a (type_instance=0x363bea0, iface_type=<value optimized out>) at gtype.c:3961 #1 0x00007ffff29fd0eb in g_object_unref (_object=0x363bea0) at gobject.c:2668 #2 0x00007ffff5932be1 in webkit_hit_test_result_dispose (object=0x7fffe01af680) at Source/WebKit/gtk/webkit/webkithittestresult.cpp:77 #3 0x00007ffff29fd1aa in g_object_unref (_object=0x7fffe01af680) at gobject.c:2697 #4 0x000000000047219b in dispose (object=0x35a1680) at ephy-embed-event.c:49 #5 0x00007ffff29fd1aa in g_object_unref (_object=0x35a1680) at gobject.c:2697 #6 0x000000000043af16 in idle_unref_context_event (window=<value optimized out>) at ephy-window.c:1969 #7 0x00007ffff20f030e in g_main_dispatch (context=0x705bb0) at gmain.c:2440 #8 g_main_context_dispatch (context=0x705bb0) at gmain.c:3013 #9 0x00007ffff20f0af8 in g_main_context_iterate (context=0x705bb0, block=1, dispatch=1, self=<value optimized out>) at gmain.c:3091 #10 0x00007ffff20f1162 in g_main_loop_run (loop=0x7963b0) at gmain.c:3299 #11 0x00007ffff4fc1c0d in gtk_main () at gtkmain.c:1358 #12 0x00000000004336c4 in main (argc=1, argv=0x7fffffffdee8) at ephy-main.c:747
Attachments
Priit Laes (IRC: plaes)
Comment 1 2011-05-07 00:26:35 PDT
*** This bug has been marked as a duplicate of bug 59799 ***
Note You need to log in before you can comment on or make changes to this bug.