firefox-bin crashed with SIGSEGV in JS_DHashTableOperate()

Bug #148733 reported by Stephen Tyrrell
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: firefox

Crashed on launch of firefox application. First thing I noted was the crash dialog, the app never appeared. Subsequent launch was successful.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Wed Oct 3 21:59:17 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/firefox/firefox-bin
NonfreeKernelModules: nvidia
Package: firefox 2.0.0.6+2-0ubuntu4
PackageArchitecture: amd64
ProcCmdline: /usr/lib/firefox/firefox-bin
ProcCwd: /home/stephen
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
StacktraceTop:
 JS_DHashTableOperate ()
 ?? ()
 ?? () from /usr/lib/firefox/libmozjs.so
 ?? () from /usr/lib/firefox/libmozjs.so
 JS_GC () from /usr/lib/firefox/libmozjs.so
Title: firefox-bin crashed with SIGSEGV in JS_DHashTableOperate()
Uname: Linux jupiter 2.6.22-12-generic #1 SMP Sun Sep 23 20:03:18 GMT 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Stephen Tyrrell (tyrrell-stephen) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:XPCWrappedNativeProto::JSProtoObjectFinalized (this=0x74f440, cx=<value optimized out>,
js_FinalizeObject (cx=0xbc3c00, obj=0x13bd070) at jsobj.c:2745
js_GC (cx=0xbc3c00, gckind=GC_NORMAL) at jsgc.c:3032
JS_GC (cx=0xbc3c00) at jsapi.c:1873
nsJSContext::ScriptEvaluated (this=0x9122d0, aTerminated=7183560) at nsJSEnvironment.cpp:2135

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

maybe one of your extensions caused this crash. firebug for instance is known to cause instabilities for some users.

Anyway, we have to wait for at least one duplicate before investigating closer.

Thanks,
 - Alexander

Changed in firefox:
status: New → Incomplete
Revision history for this message
wolfger (wolfger) wrote :

Over 4 months without a response. We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in firefox:
status: Incomplete → Invalid
Revision history for this message
Oscar Guzmán (oegr) wrote :

Something with the java is going wrong.
When I try to get the last java the firefox crash and when I visit a java based web site.

Revision history for this message
Laurent Suchet (laurent-s3) wrote :

Same thing than above, Firefox crash when going on a java website.

laurent@laurent-desktop:~$ sudo update-alternatives --config java
Il existe 2 choix pour l'alternative java (qui fournit /usr/bin/java).

  Sélection Chemin Priorité État
------------------------------------------------------------
* 0 /usr/lib/jvm/java-6-openjdk/jre/bin/java 1061 mode automatique
  1 /usr/lib/jvm/java-6-openjdk/jre/bin/java 1061 mode manuel
  2 /usr/lib/jvm/java-6-sun/jre/bin/java 63 mode manuel

I'm on Lucid, up to date.

Revision history for this message
Draycen DeCator (ddecator) wrote :

Java is known to not be fully compatible with Firefox 3.6 or 3.7 yet, which could explain the crashes you two are experiencing. If apport is generating a crash report, then please open a new bug since this one was for Firefox 2.0 and many changes have been made to the software since this bug was filed.

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.