Crash when clicked on a button (triggered javascript)



15 years ago
14 years ago


(Reporter: st946tbf, Unassigned)



Windows XP

Firefox Tracking Flags

(Not tracked)



(2 attachments)



15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910

When I clicked on a button which triggered a javascript. The version is Mozilla
1.7.3.  I could not submit the crash data through quality feed back agent
because of firewall (could you please have a server listen at port 80 for
quality feedback agent).  Please see attachment for the data I save from the
quality feedback agent.

Reproducible: Didn't try
Steps to Reproduce:
I cannot consistenly produce it.

Comment 1

15 years ago
Created attachment 163433 [details]
Save of the quality feedback agent detail data.

Comment 2

15 years ago
Created attachment 163434 [details]
Attachment for the data I save from the quality feedback agent.

The attachment is a zip file.

Comment 3

15 years ago
Actually, these 2 attachments comes from different crashes.  However, they're
both similar in nature.  When I clicked on a button, a javascript is triggered,
and then it crashes.


15 years ago
Severity: normal → critical
Keywords: crash
The talkback data on its own is useless, unfortunately.  What is the talkback
incident ID?

Also, can you attach the testcase that triggers the crash?
Product: Browser → Seamonkey
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:
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.
Last Resolved: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.