311736 - Thunderbird hung when importing a very large Outlook 2003 PST file

Status: RESOLVED INCOMPLETE

(Thunderbird :: Migration, defect)

Description

[Aditya Kini]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

Tried to import a very large(approx.800 MB) Outlook 2003 PST file with over 25
regular folders and over 10 archive folders with a total of 25,000 messages.


Reproducible: Always

Steps to Reproduce:
As described above.
Actual Results:  
The Application totally froze with heavy amount of hard-disk and CPU activity.I
had to reboot the machine to get it to be stable. When i then opened
thunderbird, I noticed that some of the mail was imported, but not everything.

Expected Results:  
Imported and all the mails and contacts and not hung.

Comment 1

[Keith Page]

I was importing an outlook 2003 1.8G mail folder and got 1/3 through ( the localfolders inbox file was 490,600 KB ). Cancelling the import crashed Thunderbird. However it simply hung, no heavy cpu usage, no hdd thrashing, program was responsive simply stopped importing the file after 490,600K. I purged the thunderbird mail files and started again and it stopped at the same spot and crashed when i eventually hit cancel. Ran a repair on the pst file and tried again and it got to about the same spot, though the file was  a little smaller after the  repair.

Right now i'm importing the mail to outlook 2000 file format so i can try agin or use readpst to convert it on a linux machine. Maybe thunderbird will work on it.

Comment 2

[Wayne Mery (:wsmwk)]

Keith's work was with v1.5

Comment 3

[Wayne Mery (:wsmwk)]

Keith, do you have the same message store? (pst file)

May have been fixed 2007-04-06 by bug 182231 crash on import mails (huge
archive) from outlook 2000.  But has nothing to do with size of archive (in that case 200MB)

Comment 4

[Joshua Cranmer [:jcranmer]]

RESO INCO due to lack of response to prior comment.

If you believe this change was made in error, please respond with your reasons why, preferably by providing a response to the question in previous comment.