Failed assertion in midori_view_has_selection with webkit 1.6.1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Midori Web Browser |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Running with --g-fatal-warnings, I get the following backtrace when right-clicking, with git midori, GTK3, and webkit 1.6.1. I think a guard of if (webkit_
** CRITICAL **: WebKitDOMRange* WebKit:
Program received signal SIGTRAP, Trace/breakpoint trap.
0x00007ffff74d8083 in g_logv () from /usr/lib/
(gdb) bt
#0 0x00007ffff74d8083 in g_logv () from /usr/lib/
#1 0x00007ffff74d8412 in g_log () from /usr/lib/
#2 0x00007ffff34a7d45 in WebKit:
from /usr/lib/
#3 0x00007ffff3431f1e in webkit_
from /usr/lib/
#4 0x000000000046f46d in midori_
at ../midori/
#5 0x0000000000469efb in midori_
menu=0x82bb70, manual=0) at ../midori/
#6 0x000000000046b387 in webkit_
web_
at ../midori/
#7 0x00007ffff7b9c0e4 in g_closure_invoke () from /usr/lib/
#8 0x00007ffff7bae06a in ?? () from /usr/lib/
#9 0x00007ffff7bb76f1 in g_signal_
from /usr/lib/
#10 0x00007ffff7bb7892 in g_signal_emit () from /usr/lib/
#11 0x00007ffff3416399 in webkit_
from /usr/lib/
#12 0x00007ffff34168aa in webkit_
#13 0x00007ffff6b03c78 in ?? () from /usr/lib/
#14 0x00007ffff7b9c0e4 in g_closure_invoke () from /usr/lib/
#15 0x00007ffff7bade9f in ?? () from /usr/lib/
#16 0x00007ffff7bb74c3 in g_signal_
from /usr/lib/
#17 0x00007ffff7bb7892 in g_signal_emit () from /usr/lib/
#18 0x00007ffff6c1cbf1 in ?? () from /usr/lib/
#19 0x00007ffff6b01e33 in gtk_propagate_event ()
from /usr/lib/
#20 0x00007ffff6b02193 in gtk_main_do_event ()
from /usr/lib/
#21 0x00007ffff67777fc in ?? () from /usr/lib/
#22 0x00007ffff74cf7fd in g_main_
from /usr/lib/
#23 0x00007ffff74cfff8 in ?? () from /usr/lib/
#24 0x00007ffff74d0532 in g_main_loop_run () from /usr/lib/
#25 0x00007ffff6b011e7 in gtk_main () from /usr/lib/
#26 0x0000000000428832 in main (argc=1, argv=0x7fffffff
at ../midori/
Changed in midori: | |
status: | Fix Committed → Fix Released |
I agree (though arguably the DOM API should not run into internal errors like that).