Closed
Bug 25036
Opened 26 years ago
Closed 26 years ago
Crash on Finish after adding a few new accounts.
Categories
(SeaMonkey :: MailNews: Account Configuration, defect, P3)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
M14
People
(Reporter: laurel, Assigned: alecf)
Details
(Keywords: crash, Whiteboard: trying to get symbolic stack traces; two bugs here?)
Using 2000-01-25-15m13 commercial build on linux 6.0
Haven't yet tested with Win32 and Mac
I've crashed 2 out of 2 times so far when trying to add several new accounts
sequentially in a session. The crashes occurred after adding 2 to 4 new
accounts at once (without confirming out of the account setup dialog).
Steps:
1. I used a new profile (may happen on existing profiles, too).
2. Edit|Account Setup.
Click New Account.
Setup a POP account, use Finish (don't Cancel) at end of setup process.
DON'T close the account setup dialog.
3. Click New Account and repeat setup steps to add a few more accounts
sequentially without closing account setup dialog.
I did 2 POP, 2 IMAP, News.
First crash occurred after adding 1st IMAP (3rd account).
Second crash occurred after adding News (5th account).
Actual result: will crash after adding a few accounts, not necessarily at the
same number of accounts added.
Expected result: should be able to add many (max?) accounts at once without
crashing.
I submitted two talkback incidents: 4442337 & 4442502
http://cyclone/reports/incidenttemplate.CFM?reportID=124&style=0&tc=22&cp=1&ck1=SUser+email+address&cd1=%25laurel%40netscape%2Ecom%25&co1=like&bbid=4442502
http://cyclone/reports/incidenttemplate.CFM?reportID=124&style=0&tc=22&cp=2&ck1=SUser+email+address&cd1=%25laurel%40netscape%2Ecom%25&co1=like&bbid=4442337
Didn't crash for me adding one at a time, don't know whether we'd consider this
blocker for m13...
QA Contact: lchiang → laurel
![]() |
Assignee | |
Comment 2•26 years ago
|
||
ddduuupppee!
*** This bug has been marked as a duplicate of 24668 ***
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
![]() |
Assignee | |
Comment 3•26 years ago
|
||
oops, talked to laurel, this is not the same bug
Status: RESOLVED → REOPENED
![]() |
Assignee | |
Updated•26 years ago
|
Resolution: DUPLICATE → ---
![]() |
Assignee | |
Comment 4•26 years ago
|
||
the first stack trace looks VERY similar to #24668, so I'm reassigning to
brendan... I've just landed the new account wizard on the tip though, so this
may behave very differently
M13 builds are also having this problem
Assignee: alecf → brendan
Status: REOPENED → NEW
![]() |
||
Comment 5•26 years ago
|
||
The first talkback *might* be an echo of 24668, which makes me wonder whether
the fix was included in that build -- but we need symbolic talkback stack traces
to be sure (file and line number too).
The second talkback lacks symbols too, but it's completely different: in xpcom
called from gecko. Should be a separate bug, if you can reproduce it.
/be
I could not reproduce this after a few run-throughs on NT 4.0 using
2000-01-25-14m13 commercial build.
![]() |
||
Comment 7•26 years ago
|
||
On M13 radar.
/be
Whiteboard: trying to get symbolic stack traces; two bugs here?
Target Milestone: M13
![]() |
||
Comment 8•26 years ago
|
||
Adding weird-JS-in-XUL-or-maybe-not crash buddies.
/be
![]() |
||
Comment 9•26 years ago
|
||
Not gonna hold M13, need more data. There are now three distinct stacks in this
bug report (or linked from it).
/be
Status: NEW → ASSIGNED
Target Milestone: M13 → M14
![]() |
||
Comment 10•26 years ago
|
||
adding grafitti to test new bugzilla feature. sorry.
![]() |
Reporter | |
Comment 11•26 years ago
|
||
Using 2000-01-25-20m13 on linux I was able to get through adding a few accounts.
Will keep an eye out, particularly when we move on to m14 builds and will
provide update comments accordingly.
Please note that I heard reports of at least one other mailnewsqa person hitting
crashes in m13 testing when adding new accounts. She will see if she can
reproduce and let me know of any talkback incidents which relate. Meantime, I
hit a crash that may be related to this or #24668, which I logged separately as
bug #25095.
![]() |
||
Comment 13•26 years ago
|
||
I bet these are all dups of the non-reentrant setTimeout timeout-firing code in
dom/src/base/nsGlobalWindow.cpp -- alecf, can you verify or just mark DUP and
close? Thanks!
/be
Assignee: brendan → alecf
Status: ASSIGNED → NEW
![]() |
Assignee | |
Comment 14•26 years ago
|
||
laurel, can you try this again? I haven't seen the crash in a when you don't use
the -mail option.
![]() |
Reporter | |
Comment 15•26 years ago
|
||
This seems to be ok at the first couple tries. I'll try some more instances,
and reopen if I do see any problem. Using 02-09-08 commercial build linux rh6.0
![]() |
Assignee | |
Comment 16•26 years ago
|
||
ok, I'm marking worksforme
the bug where the wizard crashes with -mail I believe still remains
Status: NEW → RESOLVED
Closed: 26 years ago → 26 years ago
Resolution: --- → WORKSFORME
![]() |
Reporter | |
Comment 17•26 years ago
|
||
Still am not seeing problem using 2000-02-11-11m14 commercial build linux rh6.0.
marking verified (worksforme).
Status: RESOLVED → VERIFIED
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•