Closed Bug 23864 Opened 25 years ago Closed 25 years ago

[DOGFOOD][Regression]Crash when selecting mail Inbox after migrating new profiles

Categories

(MailNews Core :: Backend, defect, P1)

defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: fenella, Assigned: sspitzer)

Details

(Whiteboard: [PDT+])

Linux REdhat 6.0 (2000-01-13-08 M13)
Win_nt 4.0 (2000-01-13-09 M13)
Steps:
1. Remove existing seamonkey profiles
2. Migrate new profiles using the installer
3. Launch Messenger using the -mail option
4. From my account, click on Inbox

Actual result: Application crashes
If I do not migrate new profiles, it works (see bug 23745)

Expected result: It should not crash.

this occurs in both POP and IMAP accounts.

Have not tested Win32 and Mac yet.
Severity: normal → critical
Summary: [Regression]Unable to select mail after migrate new profiles → [Regression]Crash when selecting mail Inbox after migrating new profiles
Summary: [Regression]Crash when selecting mail Inbox after migrating new
profiles
I try it on Win_nt 4.0, it crashes in both POP and IMAP accounts.  But if I go
back to use the previous migrated profiles, no problem.
Assignee: phil → sspitzer
Priority: P3 → P1
Target Milestone: M13
Reassign to sspitzer for M13.

Fenella, if you have a talkback ID, that would be helpful.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
today's builds were bogus.  hyatt and karnaze fixed a bunch of related bugs.
I bet this is just once instance of the bug they fixed.
on my tree, which has the fixes, this works fine.
marking as a duplicate.
try again with the new builds, when they come out.


*** This bug has been marked as a duplicate of 23832 ***
Status: RESOLVED → VERIFIED
Sure. I will mark this verified/dup.
Migrated profiles still crashing upon selecting Inbox. NT 4.0 and linux.
I'm not sure this is a part of what was fixed for #23832.
Status: VERIFIED → REOPENED
Resolution: DUPLICATE → ---
Linux REdhat 6.0 (2000-01-13-13 M13)
Win_nt 4.0 (2000-01-13-12 M13)
I agree with Laurel, I am still seeing this problem even though bug 23832 is
fixed.
On Linux, I can consistently reproduce this bug in POP and IMAP.
But on Win_nt 4.0, the crash occurs 50% of the time. I try it 3-4 times each in
POP and IMAP accounts.
I am going to re-open this bug and will try it again using tomorrow's builds.
I will check Talkback reports when it comes up.
OS: Solaris → All
QA Contact: lchiang → gbush
Summary: [Regression]Crash when selecting mail Inbox after migrating new profiles → [DOGFOOD][Regression]Crash when selecting mail Inbox after migrating new profiles
Status: REOPENED → ASSIGNED
I'm still not seeing this, I must not be doing the right steps.
laurel / fenella, after the new builds come out today, can you try it again, and
if it still happens, let me know exactly what the steps were?

I'm doing this:
I use imap in 4.x
I remove ~/.mozilla
I run mozilla -installer
once it starts up, I open messenger
click on my imap inbox (enter password, and it discovers my folders and
populates the thread pane)
click and read the message.
Whiteboard: [PDT+]
PDT+
Seth, We have not got any good build today on any platform. I shall re-test this
bug as soon as a good build comes up.
I'm going to try to reproduce this with an official (optimized) build.
perhaps it is the optimized vs. debug difference which is preventing me from
seeing the crash.
fenella is checking mac, but this looks like it is working for everyone.

hopefully, we'll be seeing a worksforme soon.
Linux Redhat 6.0 (2000-01-18-11 M13)
Win_nt 4.0 (2000-01-18-11 M13)
Mac (2000-01-17-08 M13)

After I did a clean up and migrated a new profile, I do not see any crash in the
latest build in both the POP/IMAP accounts  of the Linux and Win_nt 4.0

Mac:
POP: OK, no crash
IMAP: unable to test. see bug 24272.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → WORKSFORME
marking worksforme.
Status: RESOLVED → VERIFIED
verified on builds 20000118
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.