272017 - Crash related to threads

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Jan Rychter]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041124 Firefox/1.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041124 Firefox/1.0

Firefox suddenly crashed, console output is:

firefox-bin: ../nptl/pthread_mutex_lock.c:108: __pthread_mutex_cond_lock:
Assertion `mutex->__data.__owner == 0' failed.
/usr/bin/firefox: line 88: 12545 Aborted                 $mozbin "$@"

[2]    Done                          firefox
575.490u 80.467s 17:33:34.77 1.0%       0+0k 0+0io 236pf+0w



Reproducible: Always
Steps to Reproduce:
1.
2.
3.




This is on Gentoo Linux, x86, glibc-2.3.4.20041102 with NPTL and Firefox
compiled for Gentoo from the mozilla-firefox-1.0-r3 ebuild.

Comment 1

[timeless]

reporter; we'll need a stack trace. get your gentoo friends to help you build w/
either --enable-debug or --enable-debugger-info-modules, and make sure that you
don't build with --enable-strip or anything similarly silly. be sure to report
the exact set of build flags you're using when you comment back.

what do you mean reproducable: always? you didn't list steps. does this happen
when you first start the program? sudden crashes usually aren't always
reproducable without steps.

Comment 2

[Jan Rychter]

Unfortunately, this is not reproducible, and I've only seen it once. Sorry for
flagging this incorrectly, my mistake.

I will recompile firefox so that I can help with traces in the future. I
reported this because I was hoping that perhaps you can guess things from the
assertion message alone.

Gentoo doesn't compile with --enable-strip.

Comment 3

[timeless]

sorry, an assert like that just gives me 10 or 100 places to look and no way 
to guess what's actually happening, i need a stack trace, thanks :)

Comment 4

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 5

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.