Description of problem: Segfault with every run of CutyCapt at least under xvfb, running a VM on KVM. Version-Release number of selected component (if applicable): qt-4.6.2-20.el6.x86_64 qtwebkit-2.1.1-1.el6.x86_64 How reproducible: Always. Steps to Reproduce: 1. yum install qtwebkit qtwebkit-devel 2. svn co https://cutycapt.svn.sourceforge.net/svnroot/cutycapt 3. cd cutycapt/CutyCapt; qmake-qt4 && make 4. xvfb-run --server-args="-screen 0, 1024x768x24" ./CutyCapt --url=http://www.google.com --out=1.png Actual results: [root@test CutyCapt]# xvfb-run --server-args="-screen 0, 1024x768x24" ./CutyCapt --url=http://www.google.com --out=1.png loaded the Generic plugin can't make "generic.orientation" because no QAccelerometer sensors exist /usr/bin/xvfb-run: line 166: 2096 Segmentation fault DISPLAY=:$SERVERNUM XAUTHORITY=$AUTHFILE "$@" 2>&1 Expected results: No crash. File 1.png should contain "screenshot" of google.com Additional info: Tested (and crashed) on a fresh install of CentOS6 on a VM, with no software other than base and needed software to compile CutyCapt (gcc-c++, make, subversion, qtwebkit-devel, xvfb) Same install with qtwebkit from atrpm (qtwebkit-2.0-3.el6.x86_64) work flawlessly, even without recompiling CutyCapt.
Can you get a backtrace?
Created attachment 594807 [details] Backtrace thread apply all bt full
OK, assuming it crashed in thread 1, we have some javascript/jit fun going on: (seemingly with some, but not all debuginfo missing): Thread 1 (Thread 0x7ffff7fd2820 (LWP 3066)): #0 0x00007ffff747ed64 in FixedVMPoolAllocator (this=<value optimized out>) at ../../../JavaScriptCore/jit/ExecutableAllocatorFixedVMPool.cpp:303 No locals. #1 JSC::ExecutableAllocator::isValid (this=<value optimized out>) at ../../../JavaScriptCore/jit/ExecutableAllocatorFixedVMPool.cpp:442 No locals. #2 0x00007ffff74b6486 in ExecutableAllocator (this=0x7ffff7f0ea00, globalDataType=JSC::JSGlobalData::Default, threadStackType=JSC::ThreadStackTypeLarge) at ../../../JavaScriptCore/jit/ExecutableAllocator.h:162 No locals. #3 JSC::JSGlobalData::JSGlobalData (this=0x7ffff7f0ea00, globalDataType=JSC::JSGlobalData::Default, threadStackType=JSC::ThreadStackTypeLarge) at ../../../JavaScriptCore/runtime/JSGlobalData.cpp:148 No locals. #4 0x00007ffff74b7fa8 in create (type=JSC::ThreadStackTypeLarge) at ../../../JavaScriptCore/runtime/JSGlobalData.cpp:231 No locals. #5 JSC::JSGlobalData::createLeaked (type=JSC::ThreadStackTypeLarge) at ../../../JavaScriptCore/runtime/JSGlobalData.cpp:237 data = <value optimized out> #6 0x00007ffff6d70682 in WebCore::JSDOMWindowBase::commonJSGlobalData() () from /usr/lib64/libQtWebKit.so.4 No symbol table info available. #7 0x00007ffff6da867c in WebCore::ScriptController::getAllWorlds(WTF::Vector<WebCore::DOMWrapperWorld*, 0ul>&) () from /usr/lib64/libQtWebKit.so.4 No symbol table info available. #8 0x00007ffff705da42 in WebCore::FrameLoader::dispatchDidClearWindowObjectsInAllWorlds() () from /usr/lib64/libQtWebKit.so.4 No symbol table info available. #9 0x00007ffff705fbd5 in WebCore::FrameLoader::receivedFirstData() () from /usr/lib64/libQtWebKit.so.4 No symbol table info available.
Created attachment 594864 [details] Full Backtrace Full backtrace, now with all debuginfo's Sorry :(
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version. Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version. Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version, you are encouraged to change the 'version' to a later version prior this bug is closed as described in the policy above.
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of EPEL please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.