Description of problem: On F19 updated today (20 Mar 2013) with a brand new profile (i.e. rm -rf .mozilla), I start firefox go to "www.corriere.it" and it crashes. Here is the bt: #0 isValid (this=0xb23fb348) at /usr/src/debug/xulrunner-19.0.2/mozilla-release/js/src/jsinferinlines.h:141 #1 js::types::TypeCompartment::addPendingRecompile (this=this@entry=0xb4f49e64, cx=cx@entry=0xa8a7c200, info=...) at /usr/src/debug/xulrunner-19.0.2/mozilla-release/js/src/jsinfer.cpp:2521 #2 0x4f0cbd22 in addPendingRecompile (pc=0x0, script=..., cx=0xa8a7c200, this=0xb4f49e64) at /usr/src/debug/xulrunner-19.0.2/mozilla-release/js/src/jsinfer.cpp:2590 #3 AddPendingRecompile (pc=0x0, kind=RECOMPILE_NONE, script=..., cx=0xa8a7c200) at /usr/src/debug/xulrunner-19.0.2/mozilla-release/js/src/jsinfer.cpp:2019 #4 TypeConstraintFreezeStack::newType (this=0x9d83f308, cx=0xa8a7c200, source=0xa88bbd40, type=...) at /usr/src/debug/xulrunner-19.0.2/mozilla-release/js/src/jsinfer.cpp:2072 #5 0x4f0c41a1 in resolvePending (cx=0xa8a7c200, this=0xb4f49e64) at /usr/src/debug/xulrunner-19.0.2/mozilla-release/js/src/jsinferinlines.h:1100 #6 js::types::TypeSet::addType (this=0xa88bbd40, cx=0xa8a7c200, type=...) at /usr/src/debug/xulrunner-19.0.2/mozilla-release/js/src/jsinferinlines.h:1419 #7 0x4f0c6748 in js::types::TypeMonitorResult (cx=0xa8a7c200, script=script@entry=..., pc=0xa4525a9d ":", rval=...) at /usr/src/debug/xulrunner-19.0.2/mozilla-release/js/src/jsinfer.cpp:5359 #8 0x4f315cbe in Monitor (rval=..., pc=<optimized out>, script=..., cx=<optimized out>) at /usr/src/debug/xulrunner-19.0.2/mozilla-release/js/src/jsinferinlines.h:881 #9 UncachedInlineCall (f=..., initial=initial@entry=js::INITIAL_NONE, pret=pret@entry=0xbfffa018, unjittable=unjittable@entry=0xbfffa01c, argc=argc@entry=0) at /usr/src/debug/xulrunner-19.0.2/mozilla-release/js/src/methodjit/InvokeHelpers.cpp:372 #10 0x4f317b4e in js::mjit::stubs::UncachedCallHelper (f=..., argc=0, lowered=false, ucr=...) at /usr/src/debug/xulrunner-19.0.2/mozilla-release/js/src/methodjit/InvokeHelpers.cpp:455 #11 0x4f3014ac in js::mjit::CallCompiler::update (this=0xbfffa050) at /usr/src/debug/xulrunner-19.0.2/mozilla-release/js/src/methodjit/MonoIC.cpp:1231 #12 0x4f3017a4 in js::mjit::ic::Call (f=..., ic=<optimized out>) at /usr/src/debug/xulrunner-19.0.2/mozilla-release/js/src/methodjit/MonoIC.cpp:1312 #13 0xac074d79 in ?? () #14 0x4f503000 in ?? () from /usr/lib/xulrunner/libmozjs.so Backtrace stopped: previous frame inner to this frame (corrupt stack?) Version-Release number of selected component (if applicable): # rpm -qa |grep -E "^firefox|^glibc|^nspr|^nss" glibc-common-2.17-4.fc19.i686 nspr-4.9.5-2.fc19.i686 glibc-debuginfo-2.17-4.fc19.i686 glibc-debuginfo-common-2.17-4.fc19.i686 nspr-debuginfo-4.9.5-2.fc19.i686 nss-devel-3.14.3-10.fc19.i686 nss-util-3.14.3-1.fc19.i686 glibc-devel-2.17-4.fc19.i686 nspr-devel-4.9.5-2.fc19.i686 nss-util-devel-3.14.3-1.fc19.i686 nss-softokn-debuginfo-3.14.3-1.fc19.i686 nss-sysinit-3.14.3-10.fc19.i686 nss-softokn-freebl-3.14.3-1.fc19.i686 nss-tools-3.14.3-10.fc19.i686 nss-softokn-freebl-devel-3.14.3-1.fc19.i686 firefox-debuginfo-19.0.2-2.fc19.i686 nss-softokn-devel-3.14.3-1.fc19.i686 firefox-19.0.2-2.fc19.i686 glibc-headers-2.17-4.fc19.i686 glibc-2.17-4.fc19.i686 nss-3.14.3-10.fc19.i686 nss-softokn-3.14.3-1.fc19.i686 How reproducible: 100% Steps to Reproduce: 1. launch "firefox -g" on a clean .mozilla profile 2. Go to "www.corriere.it" 3. Crash Will attach full thread apply all bt full output as a file.
Created attachment 713176 [details] full gdb output
Interestingly enough I am unable to reproduce it on my F19 x86_64 bit box...
Can you reproduce it with a binary firefox downloaded from mozilla.org? Can you reproduce the crash in safe mode? ($firefox -safe-mode) wihout plugins? I'm unable to reproduce that on Fedoda 18/FF 19.0.2.
Hi Martin, thanks for lending a hand here. Here are the infos I was able to collect so far: - This is an F19 only issue (F18 is 100% ok) - I can reproduce the crash even when I disable all plugins by hand (same bt as in c#1) - I cannot reproduce the same crash with -safe-mode - I cannot reproduce this via official firefox from moz.org I guess we can leave this one open for a bit to see if anyone else will see this backtrace and I'll check again later on if I can still reproduce. cheers, Michele
If you can't reproduce it in safe mode it's caused by an extension you have installed. So try to remove/disable some addons you have installed and report the crash to the affected addon author.