Closed Bug 288990 Opened 20 years ago Closed 19 years ago

hangs when I try to open a custom folder with too many messages

Categories

(Thunderbird :: Account Manager, defect)

PowerPC
macOS
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: prefix, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1

In a custom folder created in the Local Folders account, I have over 1200 email
messages that have are 1) based on a Local Folders message filter and 2) moved
manually using the Run Filters on Folders from the Local Folders Input folder.

Reproducible: Always

Steps to Reproduce:
1. Double click to open the custom folder and view the contained email messages
2. The Beach Ball cursor spins indefinitely in Mac OS X 10.3.8
3. On an iMac G5, you can hear the CPU cycles increase quite a bit.

Actual Results:  
The Beach Ball cursor spins indefinitely (tested for 10 minutes).
It appears that Thunderbird was attempting to "read" the email messages.
I tested this bug three times. Each time after I force quit Thunderbird and
reopened the application, the bolded number of unread messages next to the
folder icon decreased.

Expected Results:  
Opened the custom Folder so I can view the email messages.
TB Version: version 1.0.2 (20050403)
(Built from source to debug another bug.)
OS: Linux 2.6 Kernel on Intel P4

I have found a similar problem (likely the same issue):
I opened a local folder and it crashed due to a stack overflow in

#12 0xb7504493 in nsMsgLocalMailFolder::OnStopRunningUrl (this=0x8779298, 
    aUrl=0x904274c, aExitCode=0) at nsLocalMailFolder.cpp:3293
3293        mReparseListener->OnStopRunningUrl(aUrl, aExitCode);

when mReparseListener is the same is this.

The solution might be to check mReparseListener==this before calling it recursively.

I will attach my gdb output.

For me this bug seems unreproducable, but happened after the "need to reset
thread root key" bug occurred ( using the patch from bug 269554 ).
I tried to scroll through every folder a number of times, and finally I opened
some local folders which caused the crash.

It probably can be reproduced, but maybe the *.msf files were regenerated.
Oops.  This bug is different.  I didn't read the report carefully.
I'll start a new bug with my problem.

It is probably a duplicate of bug 269554 whose patch still hasn't been applied
to Thunderbird 1.0.2.

That bug, or what causes the parent==self problem, also randomly seems to change
the # of unread messages, which was also a symptom of this bug.
Yes, my experience was also that this bug caused a change in the number of
unread messages
perhaps a dup of bug 290078?

*** This bug has been marked as a duplicate of 290078 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
not sure if this is a dup --when I looked more closely at the talkback data for
bug 290078, all of the crashes were (so far) only on Windows machines.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---

*** This bug has been marked as a duplicate of 289622 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → DUPLICATE
If this bug is considered a duplicate of bug 289622 (although the description
does not appear to match in ANY way to the bug I reported), then as of TB 1.0.2
the bug that I reported still exists and IS reproduceable EVERY time. The
particular custom local folder in question has 1400 messages. When selecting the
folder, the Mac OS X 10.3.8 spinning cursor just keeps spinning. The ONLY
resolution is a Force Quit. Though I have not used any software to measure CPU
usage, it sounds like the CPU usage and atttempt to access to disk goes way up
in per centage.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
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/
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 ago19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.