291986 - Crash triggered by dragging mail into a folder while outgoing mail is sending.

Status: RESOLVED EXPIRED

(Thunderbird :: General, defect)

Description

[Doug George]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Build Identifier: version 1.0.2 (20050317)

Drag mail from your inbox into a folder to save it.  At the same time, have an 
outgoing mail message sending.  If you drop the mail at just the right moment, 
when the outgoing mail is trying to copy itself into the Sent box, things 
screw up. 

Several different symptoms may emerge.  The folder you were dragging into may 
suddenly sprout an "unread" empty e-mail with a date in 1969.  Click on that 
and Thunderbird will crash.  

Sometimes you will get into a state where the Inbox will keep scrolling to the 
bottom continuously for no apparent reason.  Once you are in this state, 
Thunderbird will crash within a minute or two. 

Very often certain folders will simply become unavailable; if you try to move 
mail into them, nothing happens.  Again, program is unstable at this point.

Recovery requires deleting the offending MSF files.  That's fine, except that 
it happens rather frequently.  I should also mention that my folders are 
rather large, and it seems to happen more frequently the larger they get.  As 
a result, I've started making subfolders to hold older e-mails. 






Reproducible: Sometimes

Steps to Reproduce:
1.  Make a folder and fill it with lots of e-mail and perhaps big attachments 
(seems to increase probability)
2.  Start an e-mail sending
3.  Drag an e-mail from the Inbox to the other folder
4.  Repeat a few times; eventually if you get the timing just right so you 
drop the e-mail in just as it's copying to Sent, the problem happens.

Note:  this is the typical use case for responding to an e-mail and then 
filing the original incoming message. 

Actual Results:  
Anomalies described above happen, followed by Thunderbird crash.  Usually the 
crash happens after a minute or two, when you're trying to clean up the other 
symptoms.  Since you usually can't save in-progress e-mails to the folders 
once this has happened, I've learned to save them to file or copy to 
clipboard, shut down, kill the offending MSF files, and then restart.

Expected Results:  
Moved the file to the folder normally, without the glitches. 

This also happens in Netscape 7, so it's an old bug.

Comment 1

[Adam Hauner]

Doug George: Could you provide Talkback incident ID of your crash?

Comment 2

[David :Bienvenu]

Have you tried recent trunk builds? I did fix some issues with simultaneous
copies a few weeks ago. Though I believe there is still a crash problem out
there - talkback incident id's would tell me if it's the same crash

Comment 3

[Gervase Markham [:gerv]]

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 4

[Gervase Markham [:gerv]]

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.