build id: 1999042908 OS: windows nt 4 sp 4 talkback tracking ID: D3M09LCA here's what happened: I went to http://www.netscape.com. A pop-up ad appeared; I closed that window before it finished drawing (Pavlovian response?). Result: apprunner crashed. Expected result: no crash.

ok, the secret seems to be to close the window before it's finished drawing. if you patiently let it load, you have no problems and it closes ok as well.

Peter, any idea who should get this? Hyatt? Matejka? Or is this a Gecko issue?

My guess is Hyatt will either fix it or pass it along to danm. If it is that easy to crash then we should fix this for M5, setting p1 for m5.

using the 1999043008 build, I no longer see this happening... mystery fix?

also tried this on my win95 laptop over 28.8 dialup. the "Computing Channel" popup loaded several times and I also closed it at various stages of loading. I couldn't crash it with the 4/30 17:00 builds.. Rather than backing out the window.open changes as hyatt was thinking about proposing maybe lets let it ride for M5? are there other instances of crashes we know about? espcially with the unblocking of the QA testing that was going to depend on window.open working?

also tried this on my win95 laptop over 28.8 dialup. the "Computing Channel" popup loaded several times and I also closed it at various stages of loading. I couldn't crash it with the 4/30 17:00 builds.. Rather than backing out the window.open changes as hyatt was thinking about proposing maybe lets let it ride for M5? are there other instances of crashes we know about? espcially with the unblocking of the QA testing that was going to depend on window.open working?

moving to m6 to keep an eye out. hyatt's sez lets give it a try and leave the it in for m5.

Updating QA Contact

Fixed.

Looks good to me. 1999051708 build, NT 4.

Moving all Apprunner bugs past and present to Other component temporarily whilst don and I set correct component. Apprunner component will be deleted/retired shortly.