Closed Bug 263249 Opened 20 years ago Closed 16 years ago

Crash involving onMouseMove JavaScript for deleted objects

Categories

(Core :: DOM: Events, defect)

Other Branch
x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: nick2588, Unassigned)

References

()

Details

(Keywords: crash, stackwanted, testcase)

Attachments

(1 file)

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

On a page, I have a  < textarea >  tag that has an onMouseMove handler that does
this.select(); when I move over the text box. If I press the F5 key to make the
page refresh, a crash occurs if I move over the text box before the page
disappears. Does this make sense? I think it is because the objects are unloaded
(because the page is being changed), but the JavaScript still tries to access
that object.

Reproducible: Always
Steps to Reproduce:
1. Find or make a page with a textarea tag and an onMouseMove handler (WhatPulse
users can test this at http://whatpulse.bounceme.net/examples.php)
2. Move over the text box to ensure the onMouseMove handler is indeed working
3. Press F5 on the keyboard to force the page to reload. Before the text box
disappears, move over it with your mouse -- Firefox crashes.
Actual Results:  
A crash occurs. Windows says that the application will be closed and the Mozilla
Quality Feedback agent pops up.

Expected Results:  
The JavaScript should be unloaded first, so that moving over the text box before
the page disappears has no action occur.
Attached file Testcase
WFM Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041004
Firefox/0.10.1
Keywords: testcase
No crash on Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3)
Gecko/20041001 Firefox/0.10

Trunk only?
I cannot reproduce it on the test case page because it loads so quickly. This
requires the page to either be on a slow server or have a more complex and/or
larger (in file size) page.

FYI, this bug exists in the Firefox Preview 1.0 release on the Firefox home page.
Reporter: We need to be able to reproduce the bug to do anything about it. Could
you perhaps give us a password to login to
http://whatpulse.bounceme.net/examples.php.
Assignee: firefox → events
Component: General → DOM: Events
Keywords: stackwanted
Product: Firefox → Core
QA Contact: general → ian
Version: unspecified → Other Branch
(In reply to comment #0)
> Actual Results:  
> A crash occurs. Windows says that the application will be closed and the Mozilla
> Quality Feedback agent pops up.

Could you provide the Talkback IDs?
(In reply to comment #6)
> Could you provide the Talkback IDs?

No, the Mozilla Quality Feedback agent _NEVER_ works. It doesn't publish the
crashes, they just get queued. When I try to submit the queued reports, a
progress bar comes up and it just freezes for a while. Eventually it says
something to the affect that it can't connect to the server. Thus, there are no IDs.
reporter: please zip the directory:
%appdata%\talkback
attach that zip file to this bug.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050415
Crash while typing in textbox in testcase.
Talkback ID: TB123482G
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20051220 Firefox/1.6a1

Nicholas, can you still reproduce this crash in 1.5? This works for me in trunk and in 1.0.7.
Severity: minor → critical
Keywords: crash
no response
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: