Closed
Bug 210456
Opened 22 years ago
Closed 20 years ago
mozilla hangs when subscribe to large number of new folders
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: tater, Unassigned)
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5a) Gecko/20030623
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5a) Gecko/20030623
I am trying to migrate from Pine to Mozilla Mail. My mail lives on a remote
server, and I use IMAP to read it. I have a LOT of folders, over 750 of them. I
rearranged them into a hierarchy of files in folders in my home server account's
~me/mail directory, and updated my .mailboxlist to match it.
I open Mozilla, go into the subscribe area, and make sure I am subscribed to the
new mailbox files in their new locations. Both now, and before when there was
just the one long list of mailboxes, Mozilla seems to get stuck somewhere. I am
using the Mac OS X version, and all of the options under the 'Mozilla' menu
other than "About Mozilla" disappear. I have to manually kill the mozilla-binary
process to get it to quit (a not-uncommon problem with the latest build, btw -
too many select fields on a web page can cause the same stuckness).
Reproducible: Sometimes
Steps to Reproduce:
1. Create an account with hundreds of mailboxes
2. Set up a Mozilla Mail profile pointing at that account, using IMAP. Initially
only
subscribe to a few mailboxes.
3. Change your subscriptions to include all of the mailboxes.
4. Try to do stuff.
Actual Results:
Mozilla takes a nap.
Expected Results:
Opened the folder, or moved the messages to Junk, or displayed the new mail -
anything
This is probably going to be impossible to reproduce but maybe the 'Mozilla' menu
disappearing will at least point people towards some kind of better error-catching.
Updated•21 years ago
|
Product: Browser → Seamonkey
Updated•20 years ago
|
Assignee: sspitzer → mail
Comment 1•20 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 2•20 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•