Closed
Bug 317455
Opened 20 years ago
Closed 17 years ago
freeze if DOM branch is modified while viewed in DOM Inspector
Categories
(Other Applications :: DOM Inspector, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: levik, Unassigned)
Details
(Keywords: hang)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Whenever I inspect the DOM tree of a document using the DOM inspector, if any client-side code executes changing or removing the node I happen to be looking at, the whole browser freezes (including all other windows) and CPU use goes way up.
The only way I found to get out of this state is by manually killing all the firefox processes.
I'm sure this is a pretty difficult bug to encounter, but it seems to be very consistent, and hampers rich web application development quite a bit.
Reproducible: Always
Steps to Reproduce:
Comment 1•20 years ago
|
||
Can you test this with the latest version?
http://www.mozilla.org/projects/firefox/
Comment 2•20 years ago
|
||
This happened to me all the time on FF 1.0 (WinXP). But it's completely WFM with 1.5 -- I just tested using both removeChild() and innerHTML="" and was unable to make anything bad happen.
Maybe this bug should be marked 1.0 Branch only?
Updated•20 years ago
|
Assignee: nobody → dom-inspector
Component: General → DOM Inspector
Keywords: hang
Product: Firefox → Other Applications
QA Contact: general → timeless
Updated•19 years ago
|
Assignee: dom-inspector → nobody
QA Contact: timeless → dom-inspector
Comment 3•17 years ago
|
||
WFM per comment 2
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
Version: unspecified → 1.0 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•