110581 - automated get messages while compacting folders can destroy contents of inbox

Status: VERIFIED INVALID

(MailNews Core :: Backend, defect)

Description

[Forest Hale]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010913
BuildID:    2001091311

I did not think it was getting messages, and chose compact folders, it proceeded
to get the messages (at this point I got worried, since it was also compacting
folders at the same time), and though the program did not crash, I found myself
staring at an empty inbox, losing the messages that were in it already, and the
ones just downloaded, I closed and reopened mozilla and it was still empty, the
file is 0 bytes, and I have given up hope of retrieving them, thankfully I only
lost about 60 messages, as I had moved the older ones from my inbox into another
folder only the day before, I consider this a very severe bug...

Tried to reproduce it but failed, it may involve specific timing between
messages, or it may be related to the fact I had moved a lot of messages out the
day before, I think compact folders has to take a while for it to occur (perhaps
recieving more of a message, while it is compacting).

Reproducible: Couldn't Reproduce
Steps to Reproduce:
(with automatic get messages already enabled)
1. make sure your inbox has a lot of messages and is in need of compact folders
1. email yourself a few emails
2. restart mozilla (to cause automated get messages when the mail window opens)
3. choose compact folders before it begins downloading the messages.

Actual Results:  Lost 60 messages in inbox originally, was unable to reproduce,
may be timing related.  (compact folders being active while it recieves a new
packet of an incoming message?)

Expected Results:  Expected it to not lose messages.

Comment 1

[Matthias Versen [:Matti]]

This should be fixed with a more recent build.

marking invalid (your build is too old, please reopen if you see this with a
recent nightly build)

Comment 2

[Sheela Ravindran]

Reporter,
Reopen the bug if this happens on a more recent build. For now verifying.