Bug 531401

Summary: [abrt] crash detected in firefox-3.5.3-1.fc12 (in nanojit)
Product: [Fedora] Fedora Reporter: Place Holder <placeholder>
Component: firefoxAssignee: Martin Stransky <stransky>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: dwmw2, gecko-bugs-nobody
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:513519916c409080ebd967b61c97b3e6e6cd1a36
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-02-17 14:42:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Place Holder 2009-10-28 03:05:56 UTC 
abrt detected a crash.


How to reproduce
-----
1.
2.
3.


Additional information
======


Attached files
----
backtrace

cmdline
-----
/usr/lib/firefox-3.5.3/firefox 


component
-----
firefox


executable
-----
/usr/lib/firefox-3.5.3/firefox


kernel
-----
2.6.31-23.fc12.i686


package
-----
firefox-3.5.3-1.fc12


reason
-----
Process was terminated by signal 11
Comment 1 Place Holder 2009-10-28 03:05:59 UTC 
Created attachment 366375 [details]
File: backtrace
Comment 2 Martin Stransky 2009-10-30 09:41:25 UTC 
310     LInsp LirBufWriter::ins0(LOpcode op)
311     {
312         ensureRoom(1);
313         LirBuffer *b = this->_buf;
314         LInsp l = b->next();
315         l->initOpcode(op); <<<<
316         b->commit(1);
317         b->_stats.lir++;
318         return l;
319     }

#5  nanojit::LirBufWriter::ins0 (op=<value optimized out>, this=0x1003)
    at nanojit/LIR.cpp:315
        b = 0xb7d74ec0
        l = 0x1003

'l' doesn't look valid....
Comment 3 Martin Stransky 2009-10-30 10:11:11 UTC 
Reporter, can you provide any reproduction steps?
Comment 4 Place Holder 2009-11-02 03:57:59 UTC 
Hmm... unfortunately the whole abrt thing was new to me and I was just trying out the F12 alpha 3 build on a USB stick to see what's new in F12.  All I had done at that point was boot the system from the USB.  I had quickly looked around a little bit, and then attempted to launch FF to see what version was included.  FF never launched, and instead I got abrt showing up.  I also had some warnings from SELinux around the same time.  Basically, as far as FF was concerned, it was just an attempt to launch.  I must say, that after I patched the OS up to some newer code (which doesn't work that well on USB, but seemed to work initially) I was eventually able to launch FF and stopped getting the SELinux warning.

I'm not sure this is terribly helpful.. sorry about that...  but like I said.. I was just playing around with an early build of F12 and wasn't doing anything unexpected for a newly booted system.
Comment 5 Bug Zapper 2009-11-16 14:28:34 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping