Midori crashes with SIGILL Illegal Instruction when loading www.google.com
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Midori Web Browser |
New
|
Undecided
|
Unassigned |
Bug Description
(There is a similar bug on the system - last updated 2013-04-24.)
(But the dump at the prompt is quite different.)
Midori 0.5.11 i386 pre-built binaries are downloaded.
OR
Midori 0.5.11 is built from source on a Pentium3 - i386 machine. (No SSE2.)
Build is successful - no issues.
Scripting - Javascript is turned on. (On by default.)
Midori crashes when trying to load www.google.com
(When Javascript is turned off this page loads correctly.)
me@me-desktop:
Launching command: '/usr/bin/gdb' --batch -ex 'set print thread-events off' -ex run -ex 'set logging on /run/user/
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-
Vector smash protection is enabled.
Vector smash protection is enabled.
Vector smash protection is enabled.
Vector smash protection is enabled.
Program received signal SIGILL, Illegal instruction.
0xaaa50875 in ?? ()
#0 0xaaa50875 in ?? ()
#1 0xb4c861e4 in ?? () from /usr/lib/
#2 0xb4c861e4 in ?? () from /usr/lib/
#3 0xb4c862a0 in ?? () from /usr/lib/
#4 0xb4c861e4 in ?? () from /usr/lib/
#5 0xb4c861e4 in ?? () from /usr/lib/
#6 0xb4c861e4 in ?? () from /usr/lib/
#7 0xb4c82c42 in ?? () from /usr/lib/
#8 0xb4c25cc8 in JSC::JITCode:
#9 0xb4c0952d in JSC::Interprete
#10 0xb4d3969d in JSC::evaluate(
#11 0xb6391f7e in ?? () from /usr/lib/
#12 0xb639226c in ?? () from /usr/lib/
#13 0xb6566ac7 in ?? () from /usr/lib/
#14 0xb6566fd6 in ?? () from /usr/lib/
#15 0xb6745a91 in ?? () from /usr/lib/
#16 0xb67463c3 in ?? () from /usr/lib/
#17 0xb672f734 in ?? () from /usr/lib/
#18 0xb672f7e5 in ?? () from /usr/lib/
#19 0xb67312cf in ?? () from /usr/lib/
#20 0xb673169c in ?? () from /usr/lib/
#21 0xb6731beb in ?? () from /usr/lib/
#22 0xb64ec122 in ?? () from /usr/lib/
#23 0xb68a2bdf in ?? () from /usr/lib/
#24 0xb6894f32 in ?? () from /usr/lib/
#25 0xb61af980 in ?? () from /usr/lib/
#26 0xb6893663 in ?? () from /usr/lib/
#27 0xb6894417 in ?? () from /usr/lib/
#28 0xb68793f7 in ?? () from /usr/lib/
#29 0xb68795f3 in ?? () from /usr/lib/
#30 0xb68ec373 in ?? () from /usr/lib/
#31 0xb68ec586 in ?? () from /usr/lib/
#32 0xb68e0e6c in ?? () from /usr/lib/
#33 0xb71569ed in ?? () from /usr/lib/
#34 0xb5381a25 in ?? () from /usr/lib/
#35 0xb53aa490 in ?? () from /usr/lib/
#36 0xb53aa4db in ?? () from /usr/lib/
#37 0xb7d7c410 in ?? () from /lib/i386-
#38 0xb7d7fb9b in g_main_
#39 0xb7d7ff89 in ?? () from /lib/i386-
#40 0xb7d80339 in g_main_loop_run () from /lib/i386-
#41 0xb5c307a5 in gtk_main () from /usr/lib/
#42 0x0804afcf in main (argc=1, argv=0xbffff314) at /home/me/
me@me-desktop:
What version of WebKitGTK+ are you using (this can be found at <about:version>)? This seems to be a webkit bug in JSCore. Does setting the environment variable "JavaScriptCore UseJIT" to 0 avoid the crash?