25095 - Crash (sometimes) when clicking Next in new accout wizard

Status: VERIFIED WORKSFORME

(SeaMonkey :: MailNews: Account Configuration, defect, P3)

Description

[laurel]

Using 2000-01-25-20m13 commercial build on linux 6.0
Saw this once last night on NT using earlier jan25 m13 build

A crash is sometimes occuring when clicking Next in the new account setup
wizard, usually in approximately the 3rd screen.

Note: may be related to bug #23668 or bug #25036, I don't know.

Steps:

1.  Launch seamonkey go to mail window.
    (I did not open or login to any account)
2.  Edit|Account Setup.
    Click New Account and proceed to enter new account information as
appropriate on each wizard screen, clicking Next after completing the screen's
information.

Result:  crash occurs sometimes when clicking Next button (before the last
screen, not at Finish).

Talkback incidents: 

Linux using jan25-20 m13:
http://cyclone/reports/incidenttemplate.cfm?bbid=4479597

NT 4.0 using jan25-14 m13:
http://cyclone/reports/incidenttemplate.cfm?bbid=4444128

Comment 1

[laurel]

OK, this is really easy to hit if you enter an invalid email address then
correct it and click Next.  For instance:
    In email address field, enter laurel2vadar and click Next.
    Alert asking you to enter a valid email address appears, OK it.
    Go back and correct the email address to read laurel@vadar and click Next.
A good percentage of the time this will result in a crash.

More talkbacks on this: 4485448  4485357  4485066

Comment 2

[Alec Flett]

ok, these are both JS Garbage Collection stack traces. Probably a different bug?

Comment 3

[Brendan Eich [:brendan]]

Dan, I'm dumping this bug on you, but it may not be yours.  It has to do with 
window.openDialog called from a timeout, and it seems to involve double-frees 
via the JS GC.  Is it possible that a window is being freed while there are 
still "timeout-encoded" pointers to it?

/be

Comment 4

[leger]

Adding "crash" keyword to all known open crasher bugs.

Comment 5

[Christopher Lam]

*** Bug 26954 has been marked as a duplicate of this bug. ***

Comment 6

[Dan M]

  Looks nasty, and I can't reproduce it (this or the much simpler dupe bug 
26954). In the first Talkback stack trace, I see openDialog called from a timeout 
as Brendan mentioned. But I don't understand how that could be the cause of the 
problem. The openDialog call has been on the stack throughout the entire lifetime 
of the wizard. This seems to me a problem with tearing down the contents of the 
window and putting up new contents as "next" is hit.
  Double frees in the JS garbage collector, eh? This is one of those cross-
discipline problems with no one owner. I could adopt it as well as anyone, but 
I'll want help and there's no way I can get to it soon. Adding Mike to the spam 
list to attract the possibility of help from the JS group.

Comment 7

[Dan M]

You know, it still doesn't happen to me, this bug or 26954. Thankfully. Is anyone 
still seeing this?

Comment 8

[laurel]

I haven't seen this for awhile. Marking verified worksforme.  We can always
reopen or log a more current example if we see again.