Content process of Qt-Fennec crashes when closing the application

RESOLVED INCOMPLETE

Status

Core Graveyard
Widget: Qt
RESOLVED INCOMPLETE
7 years ago
a year ago

People

(Reporter: Sudarsana Nagineni, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
plugin-container crashes, after several minutes of browsing and closing the main window. The crash is not reproducible always. Here's the stack.

(gdb) bt
#0  NS_StackWalk (aCallback=0x1064500 <PrintStackFrame>, aSkipFrames=2, aClosure=0x0)
    at /home/user/mozilla-central/xpcom/base/nsStackWalk.cpp:1488
#1  0x0106446e in ah_crap_handler (signum=11) at /home/user/mozilla-central/toolkit/xre/nsSigHandlers.cpp:125
#2  <signal handler called>
#3  NS_StackWalk (aCallback=0x1064500 <PrintStackFrame>, aSkipFrames=2, aClosure=0x0)
    at /home/user/mozilla-central/xpcom/base/nsStackWalk.cpp:1488
#4  0x0106446e in ah_crap_handler (signum=6) at /home/user/mozilla-central/toolkit/xre/nsSigHandlers.cpp:125
#5  <signal handler called>
#6  0x0045f422 in __kernel_vsyscall ()
#7  0x00c97651 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0x00c9aa82 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0x00c90718 in __assert_fail () from /lib/tls/i686/cmov/libc.so.6
#10 0x06f34a63 in process_responses (dpy=0xb7563000, wait_for_first_event=<value optimised out>, current_error=0xbf8e8ccc, 
    current_request=1129) at ../../src/xcb_io.c:183
#11 0x06f34fb6 in _XReply (dpy=0xb7563000, rep=0xbf8e8d00, extra=0, discard=1) at ../../src/xcb_io.c:464
#12 0x06f28847 in XSync (dpy=0xb7563000, discard=0) at ../../src/Sync.c:48
#13 0x03fcd0a5 in qt_cleanup () at kernel/qapplication_x11.cpp:2611
#14 0x03f53edf in ~QApplication (this=0xb75170e8, __in_chrg=<value optimised out>) at kernel/qapplication.cpp:1084
#15 0x010663fb in nsQAppInstance::Release () at /home/user/mozilla-central/toolkit/xre/nsQAppInstance.cpp:70
#16 0x01dced86 in ~nsAppShell (this=0xb5ef7fb0, __in_chrg=<value optimised out>)
    at /home/user/mozilla-central/widget/src/qt/nsAppShell.cpp:66
#17 0x01de5dfb in nsBaseAppShell::Release (this=0xb5ef7fb8)
    at /home/user/mozilla-central/widget/src/xpwidgets/nsBaseAppShell.cpp:54
#18 0x01dcf8c8 in nsAppShellShutdown ()
    at /home/user/mozilla-central/widget/src/xpwidgets/nsAppShellSingleton.h:86
#19 nsWidgetQtModuleDtor () at /home/user/mozilla-central/widget/src/qt/nsWidgetFactory.cpp:233
#20 0x0204490b in nsComponentManagerImpl::KnownModule::~KnownModule() ()
   from /home/user/mozilla-central/mobilebase-qt-i686-pc-linux-gnu/dist/bin/libxul.so
#21 0x02044953 in nsAutoPtr<nsComponentManagerImpl::KnownModule>::~nsAutoPtr() ()
   from /home/user/mozilla-central/mobilebase-qt-i686-pc-linux-gnu/dist/bin/libxul.so
#22 0x02044db6 in nsTArray<nsAutoPtr<nsComponentManagerImpl::KnownModule>, nsTArrayDefaultAllocator>::Clear() ()
   from /home/user/mozilla-central/mobilebase-qt-i686-pc-linux-gnu/dist/bin/libxul.so
#23 0x020405d7 in nsComponentManagerImpl::Shutdown (this=0xb75d6220)
    at /home/user/mozilla-central/xpcom/components/nsComponentManager.cpp:1018
#24 0x01ffd4ee in mozilla::ShutdownXPCOM (servMgr=0x0)
---Type <return> to continue, or q <return> to quit---
    at /home/user/mozilla-central/xpcom/build/nsXPComInit.cpp:726
#25 0x010652d8 in XRE_TermEmbedding () at /home/user/mozilla-central/toolkit/xre/nsEmbedFunctions.cpp:223
#26 0x01ed760a in mozilla::ipc::ScopedXREEmbed::Stop (this=0xb751f370)
    at /home/user/mozilla-central/ipc/glue/ScopedXREEmbed.cpp:123
#27 0x010651c7 in XRE_InitChildProcess (aArgc=2, aArgv=0xbf8e9b94, aProcess=GeckoProcessType_Content)
    at /home/user/mozilla-central/toolkit/xre/nsEmbedFunctions.cpp:510
#28 0x08049108 in main (argc=2, argv=0xbf8e9b94)
    at /home/user/mozilla-central/ipc/app/MozillaRuntimeMain.cpp:80

Comment 1

a year ago
In bug 1282866, I have removed the QT code from the Firefox tree with the approval of the active peer. That code is not currently maintained by any team.

I have looked through the bugs in the Widget: Qt bugzilla component and I believe all of these are no longer relevant because the Qt code has been removed. If you believe that this bug is still valid, please move it to another more appropriate bugzilla component as you reopen it.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → INCOMPLETE
(Assignee)

Updated

a year ago
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.