Closed Bug 102436 Opened 23 years ago Closed 23 years ago

crash if I close the find dialog when the alert message pops up

Categories

(SeaMonkey :: UI Design, defect)

Other
FreeBSD
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: alfred, Assigned: danm.moz)

References

Details

(Keywords: crash, stackwanted)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.3) Gecko/20010914 BuildID: 0000000000 0.9.3 (FreeBSD ports build) If you try a word search in the document you are browsing and mozilla does not find any more occurences then a alert message pops up. If you focus the find dialog behind the alert message and press Escape then mozilla core dumps. Reproducible: Always Steps to Reproduce: 1. Find in this page (ctrl+f) 2. search for 'something that is not in the page' 3. click and focus the find dialog window behind the alert 'text not found' message window 4. press the Escape key Actual Results: step 4 should make mozilla core dump Expected Results: restrict focus after clicking the find button. restrict focus until alert message is destroyed. I found this bug by searching and holding down the enter button while flying by all my find results, until I hit the bottom of the page. Because I was holding down enter I queued about 5 alert messages (another bug that will be inherently fixed by fixing this bug) causing the focus to toggle between the parent find dialog window and the child alert message. I then pressed the escape key and the focus happened to land on the find dialog, then bam! core dump.
Keywords: crash
simon, iirc you might've shown me this bug in the past...d'you recall the bug # offhand? [will search in a bit...]
Whiteboard: dupeme?
I do not recall. This would be a bug for danm, I think.
Need a stacktrace
Keywords: stackwanted
Sounds like bug 70775, which mysteriously fixed itself last May. So I guess I won't close this one as a duplicate. Still, I expect this bug to fall to the same fix that 70775 was expected to fall to before it unexpectedly fixed itself. Marking dependent.
Assignee: pchen → danm
Depends on: 65521
Whiteboard: dupeme?
./RUN-Mozilla.sh -g ./mozilla-bin MOZILLA_FIVE_HOME=. LD_LIBRARY_PATH=.:./plugins LIBRARY_PATH=.:./components SHLIB_PATH=. LIBPATH=. ADDON_PATH=. MOZ_PROGRAM=./mozilla-bin MOZ_TOOLKIT= moz_debug=1 moz_debugger= /usr/bin/gdb ./mozilla-bin -x /tmp/mozargs1190 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... (no debugging symbols found)... (gdb) run Starting program: /usr/X11R6/lib/mozilla/./mozilla-bin(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. 0x28a0caac in nsEventStateManager::PreHandleEvent () from /usr/X11R6/lib/mozilla/components/libgkcontent.so (gdb) (gdb) quit The program is running. Exit anyway? (y or n) Please answer y or n. The program is running. Exit anyway? (y or n) Please answer y or n. The program is running. Exit anyway? (y or n)
Marking these all WORKSFORME sorry about lack of response but were very overloaded here. Only reopen the bug if you can reproduce with the following steps: 1) Download the latest nightly (or 0.9.6 which should be out RSN) 2) Create a new profile 3) test the bug again If it still occurs go ahead and reopen the bug. Again sorry about no response were quite overloaded here and understaffed.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
mass verification of WorksForMe bugs: to find all bugspam pertaining to this, set your search string to "IfItWorksForSlappyTheSquirrelThenItWFM". if you think this particular bug is *still* an open issue, please make sure of the following before reopening: a. that it's still a problem with ***recent trunk builds*** on the all appropriate platform[s] b. provide clear steps to reproduce (unless a good test case is already in the bug report), making sure it pertains to the original problem (avoid morphing as much as possible :)
Status: RESOLVED → VERIFIED
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.