[CRASH] crash when drawing or closing pop-up ad on netcenter

VERIFIED FIXED in M6

Status

Core Graveyard
Tracking
P1
major
VERIFIED FIXED
20 years ago
2 years ago

People

(Reporter: cpratt, Assigned: David Hyatt)

Tracking

Trunk
x86
Windows NT

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: maybe a "works for me", URL)

Attachments

(1 attachment)

(Reporter)

Description

20 years ago
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.
(Reporter)

Comment 1

20 years ago
Created attachment 81 [details]
Dr Watson log file excerpt for bug 5711
(Reporter)

Updated

20 years ago
Summary: [CRASH] → [CRASH] crash when drawing or closing pop-up ad on netcenter
(Reporter)

Comment 2

20 years ago
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.

Updated

20 years ago
Assignee: don → trudelle

Comment 3

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

Updated

20 years ago
Assignee: trudelle → hyatt
Priority: P3 → P1
Target Milestone: M5

Comment 4

20 years ago
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.
(Reporter)

Comment 5

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

Updated

20 years ago
Whiteboard: maybe a "works for me"

Comment 6

20 years ago
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?

Comment 7

20 years ago
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?

Updated

20 years ago
Target Milestone: M5 → M6

Comment 8

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

Updated

20 years ago
QA Contact: 3853 → 4137

Comment 9

20 years ago
Updating QA Contact
(Assignee)

Updated

20 years ago
Status: NEW → RESOLVED
Last Resolved: 20 years ago
Resolution: --- → FIXED
(Assignee)

Comment 10

20 years ago
Fixed.
(Reporter)

Updated

19 years ago
Status: RESOLVED → VERIFIED
(Reporter)

Comment 11

19 years ago
Looks good to me. 1999051708 build, NT 4.

Comment 12

19 years ago
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.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.