firefox crashed with SIGSEGV in JS_ValueToECMAUint32()

Bug #287433 reported by Richard J. Turner
6
Affects Status Importance Assigned to Milestone
firefox-3.0 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: firefox-3.0

Just logging-into a subscription web application I'm building and the browser died.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/firefox-3.0.3/firefox
Package: firefox-3.0 3.0.3+nobinonly-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: /usr/lib/firefox-3.0.3/firefox -no-remote
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: firefox-3.0
StacktraceTop:
 ?? () from /usr/lib/xulrunner-1.9.0.3/libmozjs.so
 ?? () from /usr/lib/xulrunner-1.9.0.3/libmozjs.so
 JS_ValueToECMAUint32 ()
 ?? () from /usr/lib/xulrunner-1.9.0.3/libxul.so
 ?? () from /usr/lib/xulrunner-1.9.0.3/libxul.so
Title: firefox crashed with SIGSEGV in JS_ValueToECMAUint32()
Uname: Linux 2.6.27-7-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare scanner tape video

Tags: apport-crash
Revision history for this message
Richard J. Turner (richard-zygous) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:js_ValueToECMAUint32 (cx=0x8a13f40, vp=0xbfd0b230) at jsnum.c:867
JS_ValueToECMAUint32 (cx=0x8a13f40, v=6815860, ip=0xbfd0b2c0) at jsapi.c:577
XPCConvert::JSData2Native (ccx=@0xbfd0b5e8, d=0xb1340a7, s=6815860,
XPCConvert::JSArray2Native (ccx=@0xbfd0b5e8, d=0xbfd0b420, s=-1282093984,
XPCWrappedNative::CallMethod (ccx=@0xbfd0b5e8, mode=XPCWrappedNative::CALL_METHOD)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in firefox-3.0:
importance: Undecided → Medium
Revision history for this message
Alexander Sack (asac) wrote :

the backtrace looks ok. do you have any chance to reproduce this? Does it goe away when you disable your extensions?

Changed in firefox-3.0:
status: New → Confirmed
Revision history for this message
Richard J. Turner (richard-zygous) wrote :

It has only happened once and I've not been able to reproduce it. I think Firebug is the only extension I have installed and that hasn't caused any problems before or since.

This happened at work, so I'll try again to reproduce it on Monday.

Revision history for this message
dino99 (9d9) wrote :

This version has expired long ago; no more supported

Changed in firefox-3.0 (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.