Red Hat Bugzilla – Bug 445513
firefox crashing in JS_GetReservedSlot
Last modified: 2008-10-24 08:34:17 EDT
Description of problem:
occasional random crashes
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. normal firefox use
Created attachment 304756 [details]
Created attachment 304757 [details]
Please install xulruner and firefox debug packages and try to catch it again.
Let me add slightly more verbiage which amounts to basically the same what
Martin was saying:
Please install firefox-debuginfo; in order to do this you have to run
Then run firefox with a parameter -g. That will start firefox running inside of
gdb debugger. Then use command run and do whatever you did to make firefox
crash. When it happens, you should go back to the gdb and run
(gdb) thread apply all backtrace
This produces usually many screens of the text. Copy all of them into a text
editor and attach the file to the bug as an uncompressed attachment.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Created attachment 305463 [details]
backtrace of all threads from core file
Hmm, unfortunately we are apparently missing just the crucial piece of information:
Thread 1 (process 25509):
#0 0x00110416 in __kernel_vsyscall ()
#1 0x008fdfe0 in raise (sig=<value optimized out>)
#2 0x0218bc3f in nsProfileLock::FatalSignalHandler (signo=<value optimized out>)
#3 <signal handler called>
#4 0x00000006 in ?? ()
#5 0x04b64359 in JS_GetReservedSlot (cx=<value optimized out>, obj=<value
index=<value optimized out>, vp=Could not find the frame base for
) at jsapi.c:4143
#6 0x021b86c5 in xpc_CloneJSFunction (ccx=<value optimized out>, funobj=<value
parent=<value optimized out>) at xpcwrappednativeinfo.cpp:76
Are you sure gdb didn't complain about missing debuginfo packages and it didn't
suggested using debuginfo-install for installing them?
Can't reproduce, please reopen if you find a reliable way how we can investigate this issue...