luakit crashed with SIGILL in execute()

[dpslxoo]

I just installed a fresh minimal ubuntu 12.04 system, first without X, then I installed xinit and xmonad. After that I installed some lightweight browsers: surf, luakit and midori.

When I start one of those browsers from commandline it works until I enter the url. Then the browser quits and on the comandline there is an error message:

Illegal instruction

After that I tried firefox and chromium which worked without problem.

Any idea for a workaround?

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: luakit 2011.07.22-r1+1015-1
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic-pae 3.2.19
Uname: Linux 3.2.0-26-generic-pae i686
ApportVersion: 2.0.1-0ubuntu11
Architecture: i386
CrashCounter: 1
Date: Mon Jul 23 08:24:45 2012
ExecutablePath: /usr/bin/luakit
ExecutableTimestamp: 1321225187
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423.2)
ProcCmdline: luakit www.google.com
ProcCwd: /var/crash
ProcEnviron:
 SHELL=/bin/bash
 TERM=xterm
 LC_MESSAGES=POSIX
 LANG=de_DE.UTF-8
Signal: 4
SourcePackage: luakit
StacktraceTop:
 ?? ()
 JSC::Interpreter::execute(JSC::ProgramExecutable*, JSC::ExecState*, JSC::ScopeChainNode*, JSC::JSObject*) () from /usr/lib/libjavascriptcoregtk-1.0.so.0
 JSC::evaluate(JSC::ExecState*, JSC::ScopeChainNode*, JSC::SourceCode const&, JSC::JSValue, JSC::JSValue*) () from /usr/lib/libjavascriptcoregtk-1.0.so.0
 ?? () from /usr/lib/libwebkitgtk-1.0.so.0
 ?? () from /usr/lib/libwebkitgtk-1.0.so.0
Title: luakit crashed with SIGILL in JSC::Interpreter::execute()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 execute (globalData=<optimized out>, callFrame=<optimized out>, registerFile=0xb6c8806c, this=0xb3befc70) at ../Source/JavaScriptCore/jit/JITCode.h:115
 JSC::Interpreter::execute (this=0xb6c88060, program=0xb3befc60, callFrame=0xb3c1fcb4, scopeChain=0xb3bfffe0, thisObj=0xb3c5ffc0) at ../Source/JavaScriptCore/interpreter/Interpreter.cpp:1139
 JSC::evaluate (exec=0xb3c1fcb4, scopeChain=0xb3bfffe0, source=..., thisValue=..., returnedException=0xbfc0fc28) at ../Source/JavaScriptCore/runtime/Completion.cpp:73
 evaluate (exception=0xbfc0fc18, thisValue=..., source=..., chain=<optimized out>, exec=0xb3c1fcb4) at ../Source/WebCore/bindings/js/JSMainThreadExecState.h:85

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[J G Miller (jgmiller)]

This bug in libjavascriptcoregtk-1.0.so.0 is still present in

PRETTY_NAME="Ubuntu quantal (12.10)"
VERSION="12.10, Quantal Quetzal"
VERSION_ID="12.10"

Package: libjavascriptcoregtk-1.0-0
Priority: optional
Section: libs
Installed-Size: 4461
Origin: Ubuntu
Maintainer: Ubuntu Developers <email address hidden>
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Architecture: i386
Source: webkit
Version: 1.10.0-0ubuntu1.1

Running freshly built from source midori 0.4.7 in gdb when trying to access http://www.google.com --

Program received signal SIGILL, Illegal instruction.
0xb5a955cb in ?? () from /usr/lib/libjavascriptcoregtk-1.0.so.0
(gdb) bt
#0 0xb5a955cb in ?? () from /usr/lib/libjavascriptcoregtk-1.0.so.0
#1 0xb5a32d7a in JSC::Interpreter::execute(JSC::ProgramExecutable*, JSC::ExecState*, JSC::ScopeChainNode*, JSC::JSObject*) ()
   from /usr/lib/libjavascriptcoregtk-1.0.so.0
#2 0xb5b148fa in JSC::evaluate(JSC::ExecState*, JSC::ScopeChainNode*, JSC::SourceCode const&, JSC::JSValue, JSC::JSValue*) ()
   from /usr/lib/libjavascriptcoregtk-1.0.so.0
#3 0xb2204b0c in ?? ()

Presumably since nobody has been assigned to this bug since it was opened almost 6 MONTHS ago, it is not regarded as important even though it affects numerous packages.

[Ronald (ronald645)]

Would like to correct my previous statement. I experience this bug with 12.10. And yes, it is still an old Athlon with no SSE2.

[pioutw (pioutw-c)]

same bug in Linux Mint 17.2 Mate & midori 0.5.11 on google with non-SSE2 CPU
planned osbolescence is in Linux too

[Herminio (herminio-hernandezjr)]

This bug can be closed. It was resoled in this bug in Debian:

http://linux.debian.bugs.dist.narkive.com/5FprjrwB/bug-771841-surf-crash-backtrace