47097 - Crash: migrating gets disk space error, cancel & select another profile, migrate.

Status: VERIFIED FIXED

(MailNews Core :: Profile Migration, defect, P3)

Description

[laurel]

Using july29 m17 commercial build NT 4.0
Haven't tried yet on mac
Linux wouldn't have multiple 4.x profiles to migrate (right?)

A crash occurs when I encounter a disk space error during migration, I cancel
the error dialog then choose a different profiles and click migrate. No talkback
in this case.

Steps to reproduce:
1.  4.x has several profiles, not yet migrated
2.  Fill your disk so there is little space left.
3.  Select a large user profile (one that is likely to get an "out of disk
space" error when migrating, would depend on profile and amount of space left on
disk...).  Migrate the large-ish profile.
4.  During the migration/coverting process an error displays "There is not
enough space to migrate your profile.  You can free some space and retry, create
a new empty profile or cancel."   Click Cancel.
5.  You are returned back to the Select User Profile/Manage User profiles
dialog.  Select another profile to migrate, click Start Mozilla/Netscape.
6.  (sometimes I don't get a migrate profile dialog and profile manager is
unresponsive)  When the Migrate Profile dialog appears, click OK to start the
profile migration process... crash occurs shortly thereafter.

Result:  crash occurs.

Expected:  give me an error if there's a problem, but don't crash.

Comment 1

[Grace Bush]

I was able to reproduce this also- cc'ing dbragg, racham
I used todays' M17 build 2000073105

Comment 2

[dbragg]

This wouldn't be Seth.  This is either a migration bug or a profile manager bug. 
I'll take it while investigating.

Comment 3

[Daniel Veditz [:dveditz]]

Adding nsbeta3 keyword to bugs which already have nsbeta3 status markings so 
the queries don't get all screwed up.

Comment 4

[dbragg]

The destructor was not setting mInstance to nsnull.  Fixed.

Comment 5

[laurel]

OK using 2000-08-24-08 commercial build NT 4.0

Comment 6

[laurel]

Note:  encountered problems with the migrating accounts past the steps in this
bug.  Separate bug logged -- bug 50247