When composing an email, as soon as I click the attachment button in the toolbar or choose that option from the menu, all open Mozilla applications (browser and email) crash. Using Mozilla/5.0 (X11; U; NetBSD i386; en-US; rv:1.1) Gecko/20020925 built from NetBSD package sources (mozilla-1.1nb1)
can you post stack trace using GDB and/or reproduce this with latest nightly build ?
Keywords: crash, stackwanted
Running mozilla with gdb gives the following: : : (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... ---------------------- PrepareDocumentForEditing (no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. 0x485cde92 in memcpy () from /usr/lib/libc.so.12 (gdb) q The program is running. Exit anyway? (y or n) y $
QA Contact: yulian → stephend
still happening with newer version(s)? (bug cleaning)
I have seen a similar problem with Thunderbird 1.0 running on Windows XP service pack 2. It is currently repeatable since this power up, no idea when the last time was that I succesful sent an attachment so I can't check what has changed since then and I don't know if the problem will be reproducable after after after I reboot yet. The only diference with XP is that thunderbird locks up rather than crashes but I exepct this is more to do with the the XP kernel VM rather than the bug is different. I don't think my install has the reporting agent in (plus I don't know how to force a core dump to be sent) so any advice on how I can help would be appreciated (while the bug is still reproducable).
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/
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.