272635 - crash browser when rapidly clicking a link with a target and a frameset

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[Peter]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041122
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041122

browser crashes if you click on a link really rapidly, but not too rapidly, and
then move the mouse cursor outside the browser window. i tried it over and over
and with a few tries managed to do it as long as my hrefs were to my own server... 

I managed to crash mozilla doing this only once without moving the mouse cursor
out of the window.


Reproducible: Always
Steps to Reproduce:
1. go to url: http://bronze.hopto.org/crashMozilla/remote/frameset.html
2. randomly click on the links on the left around 5-10 times per second
3. move the mouse over the right frame, and quickly out of the browser (like
over the taskbar)

it takes many tries to get it to work, but it always crashes eventually.
Actual Results:  
crash...
whenever it crashes, the right frame in the browser is blank. the page is not
loaded.


Expected Results:  
expected it to not crash...


mozilla.exe - Application Error

The instruction at "0x610d109a" referenced memory at "0x00740069". The memory
could not be "read".

Click on OK to terminate the program
Click on CANCEL to debug the program
---------------
"why would you be clicking on a link over and over?" you might ask..... well i
was trying to see if a Servlet i wrote would slow down the computer if i clicked
too fast. I was looking at the CPU usage (which btw was 95-100% used up by
mozilla while i was clicking).

Comment 1

[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 2

[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.