Closed
Bug 209851
Opened 21 years ago
Closed 21 years ago
search messages does not complete
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 209850
People
(Reporter: vdicarlo, Assigned: sspitzer)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030612 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030612 When I try to search my local folders, including subfolders, which contain a lot (407 megabytes) of data, the search stops somewhere in the middle while the status line of the search dialog displays a message saying "Building summary file for [subfolder name]". When this happens, if I look in the folder, there is nothing visible in it. If I close email and restart, the folder still appears empty. If I close Mozilla entirely, including the quickstart, everything resets and the folder is displayed properly, but repeating the same search produces a hangup at the same place. If I delete the folder, and search again, the problem occurs on another folder. The problem occurs regardless of whether the search is of the subject line or the body, but does not occur for smaller searches that encompass just the subfolder on which the search will hang if a more comprehensive search is done. Reproducible: Always Steps to Reproduce: 1. Do a search of subject line or body on Local Folders including subfolders. 2. Wait for the search to hang up with a message saying ""Building summary file for [subfolder name]" Actual Results: The search stops somewhere in the middle while the status line of the search dialog displays a message saying "Building summary file for [subfolder name]". Expected Results: Completed the search.
*** This bug has been marked as a duplicate of 209850 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
Component: MailNews: Search → MailNews: Message Display
QA Contact: laurel → search
You need to log in
before you can comment on or make changes to this bug.
Description
•