118661 2013-07-15 01:25:49 -0700 [Qt][WK1] REGRESSION(r145820): tst_QWebView::crashTests() fails after this revision. 2014-02-03 03:26:43 -0800 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) Unspecified Unspecified RESOLVED INVALID P2 Normal --- 38654 1 abrhm webkit-unassigned beidson kadam ossy zarvai oldest_to_newest 908329 0 abrhm 2013-07-15 01:25:49 -0700 stdio: QFATAL : tst_QWebView::crashTests() Received signal 11 FAIL! : tst_QWebView::crashTests() Received a fatal error. Loc: [Unknown file(0)] 908538 1 beidson 2013-07-15 15:31:51 -0700 More information is certainly needed here before anybody can even take any guesses... 1 - Is this an ASSERT in a debug build, or a "legitimate" crash? 2 - Backtrace? 3 - What is the failing test doing? 908806 2 abrhm 2013-07-16 04:13:16 -0700 I hope it helps: (gdb) run Source/WebKit/qt/tests/qwebview/ Starting program: /home/abrhm/webkit/WebKit/WebKitBuild/Debug/bin/DumpRenderTree Source/WebKit/qt/tests/qwebview/ [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe57a4700 (LWP 19098)] [New Thread 0x7fff9fdf3700 (LWP 19099)] ASSERTION FAILED: !m_controller /home/abrhm/webkit/WebKit/Source/WebCore/platform/mock/DeviceOrientationClientMock.cpp(42) : virtual void WebCore::DeviceOrientationClientMock::setController(WebCore::DeviceOrientationController*) 1 0x7ffff4c4199d /home/abrhm/webkit/WebKit/WebKitBuild/Debug/lib/libQt5WebKit.so.5(+0xe9599d) [0x7ffff4c4199d] 2 0x7ffff42df173 /home/abrhm/webkit/WebKit/WebKitBuild/Debug/lib/libQt5WebKit.so.5(_ZN15QWebPageAdapter21initializeWebCorePageEv+0x21f) [0x7ffff42df173] 3 0x7ffff7bae1ac /home/abrhm/webkit/WebKit/WebKitBuild/Debug/lib/libQt5WebKitWidgets.so.5(+0x271ac) [0x7ffff7bae1ac] 4 0x7ffff7bb0dcc /home/abrhm/webkit/WebKit/WebKitBuild/Debug/lib/libQt5WebKitWidgets.so.5(_ZN8QWebPageC2EP7QObject+0x56) [0x7ffff7bb0dcc] 5 0x423b58 /home/abrhm/webkit/WebKit/WebKitBuild/Debug/bin/DumpRenderTree() [0x423b58] 6 0x424f32 /home/abrhm/webkit/WebKit/WebKitBuild/Debug/bin/DumpRenderTree() [0x424f32] 7 0x43a4b7 /home/abrhm/webkit/WebKit/WebKitBuild/Debug/bin/DumpRenderTree() [0x43a4b7] 8 0x7ffff1b6e76d /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7ffff1b6e76d] 9 0x417419 /home/abrhm/webkit/WebKit/WebKitBuild/Debug/bin/DumpRenderTree() [0x417419] Program received signal SIGSEGV, Segmentation fault. 0x00007ffff4c419a7 in WebCore::DeviceOrientationClientMock::setController (this=0x6b82a0, controller=0x6b8320) at /home/abrhm/webkit/WebKit/Source/WebCore/platform/mock/DeviceOrientationClientMock.cpp:42 42 ASSERT(!m_controller); (gdb) bt #0 0x00007ffff4c419a7 in WebCore::DeviceOrientationClientMock::setController (this=0x6b82a0, controller=0x6b8320) at /home/abrhm/webkit/WebKit/Source/WebCore/platform/mock/DeviceOrientationClientMock.cpp:42 #1 0x00007ffff42df173 in QWebPageAdapter::initializeWebCorePage (this=0x693d50) at /home/abrhm/webkit/WebKit/Source/WebKit/qt/WebCoreSupport/QWebPageAdapter.cpp:211 #2 0x00007ffff7bae1ac in QWebPagePrivate::QWebPagePrivate (this=0x693d50, qq=0x693c90) at /home/abrhm/webkit/WebKit/Source/WebKit/qt/WidgetApi/qwebpage.cpp:204 #3 0x00007ffff7bb0dcc in QWebPage::QWebPage (this=0x693c90, parent=0x6961e0) at /home/abrhm/webkit/WebKit/Source/WebKit/qt/WidgetApi/qwebpage.cpp:1360 #4 0x0000000000423b58 in WebPage::WebPage (this=0x693c90, parent=0x6961e0, drt=0x7fffffffdbe0) at /home/abrhm/webkit/WebKit/Tools/DumpRenderTree/qt/DumpRenderTreeQt.cpp:132 #5 0x0000000000424f32 in DumpRenderTree::DumpRenderTree (this=0x7fffffffdbe0) at /home/abrhm/webkit/WebKit/Tools/DumpRenderTree/qt/DumpRenderTreeQt.cpp:423 #6 0x000000000043a4b7 in main (argc=2, argv=0x7fffffffdf08) at /home/abrhm/webkit/WebKit/Tools/DumpRenderTree/qt/DumpRenderTreeMain.cpp:138 909347 3 beidson 2013-07-17 09:30:23 -0700 It's *extremely* unlikely that this assertion was caused by r145820 Whatever's going on here, this seems very much a Qt platform-specific bug. 975764 4 jturcotte 2014-02-03 03:26:43 -0800 === Bulk closing of Qt bugs === If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it and remove [Qt] from the summary. If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines.