Bug 26553 - WebKit crashes on several websites such as facebook.com
Summary: WebKit crashes on several websites such as facebook.com
Status: RESOLVED DUPLICATE of bug 27016
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Linux
: P2 Critical
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-19 11:30 PDT by Shuo Tang
Modified: 2009-07-09 19:45 PDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Shuo Tang 2009-06-19 11:30:49 PDT
In x86_64 arch Linux platform. Nightly built of Webkit crashes in a lot of website including facebook.com, nytimes.com, espn.com, google.com/maps, etc.

I have this problem with both qt and gtk port of 65 bit webkit with JIT turned off. Here is a trace when crashing (release version of QtLauncher). As far as I know, 32 bit with JIT enabled has no problem. 

This GDB was configured as "x86_64-linux-gnu"...
(gdb) r
Starting program: /home/shuo/webkit.org/WebKit/WebKitBuild/Release/bin/QtLauncher
[Thread debugging using libthread_db enabled]
[New Thread 0x7fa70c3a9750 (LWP 11431)]
[New Thread 0x7fa701f92950 (LWP 11434)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fa70c3a9750 (LWP 11431)]
0x00007fa70b388641 in JSC::Interpreter::privateExecute ()
   from /home/shuo/webkit.org/WebKit/WebKitBuild/Release/lib/libQtWebKit.so.4
Current language:  auto; currently asm
(gdb) bt
#0  0x00007fa70b388641 in JSC::Interpreter::privateExecute ()
   from /home/shuo/webkit.org/WebKit/WebKitBuild/Release/lib/libQtWebKit.so.4
#1  0x00007fa70b38aef1 in JSC::Interpreter::execute ()
   from /home/shuo/webkit.org/WebKit/WebKitBuild/Release/lib/libQtWebKit.so.4
#2  0x00007fa70b3b5e0b in JSC::JSFunction::call ()
   from /home/shuo/webkit.org/WebKit/WebKitBuild/Release/lib/libQtWebKit.so.4
#3  0x00007fa70b397880 in JSC::call ()
   from /home/shuo/webkit.org/WebKit/WebKitBuild/Release/lib/libQtWebKit.so.4
#4  0x00007fa70b4432e2 in WebCore::ScheduledAction::executeFunctionInContext ()
   from /home/shuo/webkit.org/WebKit/WebKitBuild/Release/lib/libQtWebKit.so.4
#5  0x00007fa70b4437d0 in WebCore::ScheduledAction::execute ()
   from /home/shuo/webkit.org/WebKit/WebKitBuild/Release/lib/libQtWebKit.so.4
#6  0x00007fa70b6b5eb8 in WebCore::DOMTimer::fired ()
   from /home/shuo/webkit.org/WebKit/WebKitBuild/Release/lib/libQtWebKit.so.4
#7  0x00007fa70b735202 in WebCore::ThreadTimers::fireTimers ()
   from /home/shuo/webkit.org/WebKit/WebKitBuild/Release/lib/libQtWebKit.so.4
#8  0x00007fa70b7352ab in WebCore::ThreadTimers::sharedTimerFiredInternal ()
   from /home/shuo/webkit.org/WebKit/WebKitBuild/Release/lib/libQtWebKit.so.4
#9  0x00007fa709f034d3 in QObject::event () from /usr/lib/libQtCore.so.4
#10 0x00007fa70a3c178d in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#11 0x00007fa70a3c997a in QApplication::notify () from /usr/lib/libQtGui.so.4
#12 0x00007fa709ef375c in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#13 0x00007fa709f207f6 in ?? () from /usr/lib/libQtCore.so.4
#14 0x00007fa709f1cf0d in ?? () from /usr/lib/libQtCore.so.4
#15 0x00007fa70718020a in g_main_context_dispatch ()
   from /usr/lib/libglib-2.0.so.0
#16 0x00007fa7071838e0 in ?? () from /usr/lib/libglib-2.0.so.0
#17 0x00007fa707183a7c in g_main_context_iteration ()
   from /usr/lib/libglib-2.0.so.0
#18 0x00007fa709f1ce6f in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#19 0x00007fa70a459bef in ?? () from /usr/lib/libQtGui.so.4
#20 0x00007fa709ef2002 in QEventLoop::processEvents ()
   from /usr/lib/libQtCore.so.4
#21 0x00007fa709ef23cd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#22 0x00007fa709ef4694 in QCoreApplication::exec ()
   from /usr/lib/libQtCore.so.4
#23 0x0000000000415695 in main ()
Comment 1 Oliver Hunt 2009-07-09 19:45:40 PDT

*** This bug has been marked as a duplicate of bug 27016 ***