[GUTSY] firefox crashed [@MarkGCThingChildren] [@fun_mark] [@js_Mark]

Bug #136414 reported by Marco Maini
6
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Invalid
High
Mozilla Bugs

Bug Description

Binary package hint: firefox

... firefox-bin crashed with SIGSEGV in raise()

I don't know if this problem is related to strange issues in Firefox, also described in bug report 77625.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Aug 31 14:00:35 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/firefox/firefox-bin
NonfreeKernelModules: cdrom
Package: firefox 2.0.0.6+2-0ubuntu3
PackageArchitecture: i386
ProcCmdline: /usr/lib/firefox/firefox-bin
ProcCwd: /home/marco
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: firefox
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 raise () from /lib/tls/i686/cmov/libpthread.so.0
Title: firefox-bin crashed with SIGSEGV in raise()
Uname: Linux maini-desktop 2.6.22-10-generic #1 SMP Wed Aug 22 08:11:52 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Extracted from symbolized stacktrace:
(file: http://launchpadlibrarian.net/9381439/gdb.log)
...
#3 <signal handler called>
#4 MarkGCThingChildren (cx=0x85fb1c0, thing=0x89c5160, flagp=0x89c5534 "\020", shouldCheckRecursion=1) at jsgc.c:2065
#5 fun_mark (cx=0x85fb1c0, obj=0x89deb78, arg=0x0) at jsfun.c:1453
#6 js_Mark (cx=0x85fb1c0, obj=0x89deb78, arg=0x0) at jsobj.c:4845
#7 MarkGCThingChildren (cx=0x85fb1c0, thing=0x89deb78,
#8 MarkGCThingChildren (cx=0x85fb1c0, thing=0x0, flagp=0x85fb1c0 "|­\020\bÀ${\b", shouldCheckRecursion=1) at jsgc.c:2093
#9 MarkGCThingChildren (cx=0x85fb1c0, thing=0x0, flagp=0x85fb1c0 "|­\020\bÀ${\b", shouldCheckRecursion=1) at jsgc.c:2093
#10 MarkGCThingChildren (cx=0x85fb1c0, thing=0x0, flagp=0x85fb1c0 "|­\020\bÀ${\b", shouldCheckRecursion=1) at jsgc.c:2093
#11 gc_root_marker (table=0x810ab00, hdr=0x89bf7e4, num=4, arg=0x85fb1c0) at jsgc.c:2516
#12 JS_DHashTableEnumerate (table=0x810ab00, etor=0xb7f615b0 <gc_root_marker>, arg=0x85fb1c0) at jsdhash.c:674
...

Revision history for this message
Marco Maini (maini10) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()
?? ()
?? ()
raise () from /lib/tls/i686/cmov/libpthread.so.0

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
Revision history for this message
Hilario J. Montoliu (hjmf) (hmontoliu) wrote : Report Needed

Thank you Marco Maini for submitting this report.

Unfortunately this report lacks information we need to investigate it further.
Of course this is not your fault, but the coredump attached to your report
doesn't provide useful information for us.

Could you please try to obtain a backtrace by following the instructions on [1]
and upload it to [2].

Please if this crash is reproducible describe the steps that lead to it (it is
very important for us to have a test case for each crash). Also, confirm if
possible, that the crash is reproducible after disabling your third party
extensions.

This will greatly aid us in tracking down your problem.

Thanks in advance.

H. Montoliu

[1] https://wiki.ubuntu.com/MozillaTeam/Bugs
[2] https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/136414/+addcomment

description: updated
Changed in firefox:
assignee: nobody → mozilla-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Marco Maini (maini10) wrote : Re: [GUTSY] firefox crashed

Backtrace of this crash. Feel free to ask more information.

Revision history for this message
Hilario J. Montoliu (hjmf) (hmontoliu) wrote :

Thank you for your feedback Marco,

Could you please provide a detailed description of how to reproduce this crash?

Thanks in advance.

description: updated
Changed in firefox:
importance: Medium → High
Revision history for this message
Hilario J. Montoliu (hjmf) (hmontoliu) wrote :

We have not received any duplicates for some time. Thus, this crash was likely due to some unique plugin extension combination or has been fixed in the meantime. Please, reopen it at any time if you have more related info.

Thanks for your contribution. Don't hesitate to submit new crashes,

H. Montoliu

Changed in firefox:
status: Incomplete → 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.