Red Hat Bugzilla – Bug 982025
[abrt] seamonkey-2.17.1-1.fc19: nsProfileLock::FatalSignalHandler: Process /usr/lib/seamonkey/seamonkey was killed by signal 11 (SIGSEGV)
Last modified: 2013-07-16 08:28:24 EDT
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#2 nsProfileLock::FatalSignalHandler at /usr/src/debug/seamonkey-2.17.1/comm-release/objdir/mozilla/toolkit/profile/nsProfileLock.cpp:180
#4 isValid at /usr/src/debug/seamonkey-2.17.1/comm-release/mozilla/js/src/jsinferinlines.h:141
#5 js::types::TypeCompartment::addPendingRecompile at /usr/src/debug/seamonkey-2.17.1/comm-release/mozilla/js/src/jsinfer.cpp:2572
#6 addPendingRecompile at /usr/src/debug/seamonkey-2.17.1/comm-release/mozilla/js/src/jsinfer.cpp:2641
#7 AddPendingRecompile at /usr/src/debug/seamonkey-2.17.1/comm-release/mozilla/js/src/jsinfer.cpp:2086
#8 TypeConstraintFreezeStack::newType at /usr/src/debug/seamonkey-2.17.1/comm-release/mozilla/js/src/jsinfer.cpp:2139
#9 resolvePending at /usr/src/debug/seamonkey-2.17.1/comm-release/mozilla/js/src/jsinferinlines.h:1114
#10 js::types::TypeSet::addType at /usr/src/debug/seamonkey-2.17.1/comm-release/mozilla/js/src/jsinferinlines.h:1433
#11 SetArgument at /usr/src/debug/seamonkey-2.17.1/comm-release/mozilla/js/src/jsinferinlines.h:1054
#13 js::types::TypeMonitorCallSlow at /usr/src/debug/seamonkey-2.17.1/comm-release/mozilla/js/src/jsinfer.cpp:5286
Created attachment 770174 [details]
Created attachment 770175 [details]
Created attachment 770176 [details]
Created attachment 770177 [details]
Created attachment 770178 [details]
Created attachment 770179 [details]
Created attachment 770180 [details]
Created attachment 770181 [details]
Created attachment 770182 [details]
Created attachment 770183 [details]
Seamonkey seems incredibly unstable while browsing Facebook.
This same version worked fine on Fedora 17 until the system
The backtrace seems to implicate libstdc++.so.6, but this comes
from the package libstdc++-4.8.1-1.fc19.i686 which verifies OK
with rpm -V.
cmdline: /usr/lib/seamonkey/seamonkey -new-instance
reason: Process /usr/lib/seamonkey/seamonkey was killed by signal 11 (SIGSEGV)
runlevel: N 5
According to http://www.seamonkey-project.org/releases/seamonkey2.19/#issues, there is an upstream issue related to "profile locking". And we see "nsProfileLock" in the backtrace. May be something related?...
Could you please test the latest seamonkey-2.19 from updates-testing?
Also, seamonkey-2.17 is based on the same code as Firefox-20, and seamonkey-2.19 shares code with firefox-22 . It could be useful to know whether the correspond version of Firefox has the same issue or not...
Sorry it didn't occur to me to look in updates-testing. I have now done that and seamonkey-2.19 seems to work fine. Thanks.