This morning's build. Run apprunner. Click on the throbber (you go to netscape). Then I moved the window, and hit: Assertion failure: 0, at macsockotpt.c:1720 Then, click on the link at the top right (the little running guy with the envelope, but apparently other links are just as bad). You crash calling NET_ClearReadSelect() with a freed active-entry pointer, in NET_ProcessHTTP() line 3496. Assigning to gordon (who recently checke in some macsock-type changes, and dp, who should know about this.

Moved priority to P1, since it's a crasher.

Putting on M3 radar

OK, it turns out that I just clicked on the one link that causes the crash. The URL is the one for the AIM 2.0 promotion: see the URL above.

More evidence: This URL doesn't work on windows, either. But on Windows, it just produces a blank page (on Macintosh, it crashes). Changing platform to ALL. If you type in the URL: 1. it works on Macintosh, but 2. on windows, the apprunner window just disappears! On Macintosh, the crash only occurs when you use the image map to get there. Assigning to chofmann, because we don't know whom else to assign it to.

lets try dp. can we get some stack traces added to the bug?

On NT4.0 if I type in the above url in the text field, things work ok. Gordon, could you give us the mac stack trace (don said I could ask you that).

beppe- please check with latest build on all platforms. Note results here and have tester run the full build and get a Talkback report for the engineer please.

We were testing this on John McMullen's machines. I don't have a Windows build, and on my Mac build it locks the machine, so I can't get a stack crawl. Maybe John can.

using the 3/16 build -- apprunner win32 - no crashing, all selections resulted in going to the targeted page successfully mac - no crashing, all selections resulted in going to the targeted page successfully linux - no crashing, all selections resulted in going to the targeted page successfully

They must have fixed their content on this AOL page, because I just tried it again (in order to get the stack crawl) and it didn't fail. The windows failure did not occur, either. However, this bothers me, because illegal javascript (or whatever it was) should not crash the client. I fear we have to mark this "WORKSFORME", though we may have lost a valuable test case, unless we can get back this page in the form that it was in yesterday. Changing to "worksforme".

using the 3/16 build -- apprunner win32 - no crashing, all selections resulted in going to the targeted page successfully mac - no crashing, all selections resulted in going to the targeted page successfully linux - no crashing, all selections resulted in going to the targeted page successfully

Moving from Apprunner to Other component temporarily whilst don and I set proper component. Apprunner component will be retired/deleted shortly.