Closed Bug 386941 Opened 19 years ago Closed 18 years ago

Invoking DOM Inspector in Composer Windows causes Seamonkey to hang

Categories

(SeaMonkey :: Composer, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: francis.turner, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2 Mnenhy/0.7.5.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2 Mnenhy/0.7.5.0 When using composer to create a web page if the user accidentally presses CTRL-SHIFT-I the DOM inspector pops up blank and SeaMonkey then hangs forever. All SeaMonkey windows (browsers, email etc.) are affected. Trying to close the DOM Inspector window brings up the Windows XP "xxx is not responding" message and offers to close offending application. This kills all of SeaMonkey not just the DOM window. Reproducible: Always Steps to Reproduce: 1.Open a composer window 2.Type something in 3.Press CTRL-SHIFT-I Actual Results: DOM Inspector window opens and Seamonkey hangs Expected Results: Either the DOM inspector should open properly or it should not open at all. This may be related to stuff discussed here: https://bugzilla.mozilla.org/show_bug.cgi?id=109682#c16
Tested this in my Linux build : (Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a7pre) Gecko/200707051111 SeaMonkey/2.0a1pre) There it works fine and no problems
A bit more checking. step 3 in the steps to reproduce should be Type in some text, pressing CTRL-SHIFT-I in the middle and continue typing rapidly. It looks to me like the problem is due to the additional characters being entered as the DOM inspector is starting up. If you just press CTRL-SHIFT-I and wait the problem does not occur. It should be noted that the way I discovered the bug was to try to type in a sentence containing an uppercase I and accidentally hitting both shift and crtl at the same time.
1.1.9 does not crash. Please reopen this report if you still experience this issue with the latest release. Thanks. http://www.seamonkey-project.org/releases/
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
Agree . Cannot reproduce in 1.1.9
You need to log in before you can comment on or make changes to this bug.