Closed Bug 308090 Opened 19 years ago Closed 19 years ago

Crash if search without interrupting previous search

Categories

(SeaMonkey :: MailNews: Message Display, defect)

1.7 Branch
x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 301180

People

(Reporter: abl, Unassigned)

Details

(Keywords: crash)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.11) Gecko/20050728 MultiZilla/1.8.1.0h
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.11) Gecko/20050728 MultiZilla/1.8.1.0h

Mozilla crashes if i search another text in inbox without interrupting previous
search (tested with clean profile (all extensions installed into profile, so i
have clean account for testing) and default theme). Tested with keyboard,
because most of time i use just keyboard shortcuts...

Reproducible: Always

Steps to Reproduce:
1. Open MailNews window.
2. Press Ctrl + Shift + F. Search window should come up. 
3. Select "Body" if you don't have lots of msg in inbox, o just leave defaults.
4. Enter search term, press enter. Mozilla starts searching.
5. So, it looks you did a mistake. Clear some symbols in search term, and press
enter again (previous search is running)

If search lasts not long, search by body content. Example - i need mails with
word "crash", entered "carsh" and pressed "enter", after second pressed "Esc"
(as "Cancel" shortcut), corrected typo "carsh" into "crash" and pressed "enter"
again.
Actual Results:  
Mozilla crashes. No talkback window.

Expected Results:  
I use "Esc" key as shortcut to most windows dialog windows, but this don't works
in search - if u press "Esc" when searching, nothing happens. So, results should
be "stopped previous search, and started new".

*** This bug has been marked as a duplicate of 301180 ***
Severity: major → critical
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Keywords: crash
Resolution: --- → DUPLICATE
Version: unspecified → 1.7 Branch
Component: MailNews: Search → MailNews: Message Display
You need to log in before you can comment on or make changes to this bug.