* TITLE/SUMMARY ss: www.hardradio.com crashes Win NT (2 frames filled w/bitgunk on ’98) * STEPS TO REPRODUCE 0) Point viewer or xpviewer to http://ww.hardradio.com Click on the gateway image located below the "Click to Enter" text label. (or just go directly to http://www.hardradio.com/hr3lead.html; doesn’t matter.) * RESULT - What happened NT: Crashes Viewer & XPViewer. Talkback tracking ID of KXM54OKO (for XPViewer crash.) Win98: The top and bottom frames are filled entirely with visual garbage. The top frame looks like the background JPG file, dragged across horizontally; a 2 pixel wide set of garbage pixels with similar colors to the JPG file, repeated throughout the width of the frame. The bottom frame looks like purely random multicolored pixels, like what we used to see prior to doing an HGR on an Apple 2 as it cleaned out the crud in RAM. On XPViewer, while the page is finished loading (Stop button disabled), the app still displays a cycle of "Connect: Host www.hardradio.com contacted. Waiting for reply" and "Connect: Contacting Host....". * REGRESSION - Occurs On viewer.exe (11.23.98a build used) xpviewer.exe (11.23.98a build used) - Doesn't Occur On Communicator 4.5 for Win32 (RTM Complete build used) * CONFIGURATIONS TESTED - Windows NT 4.0 SP 3, 96 MB RAM. - Windows 98, 48 MB RAM

Using 11.24.98 build, can't reproduce crash on Win NT. Top and bottom frames remain completely munged as described in bug. Thus, eliminating "ss:" from bug title, and degrading priority/severity a notch.

(...or on Win 98)

(...or using viewer instead of xpviewer)

Looks like a duplicate of recent URL problem

Re-assigned to gagan@netscape.com. Gagan, is this a netlib bug? Who should get this?

May have been related to the caching bugs.

No crash on 1.25.99 builds running on NT 4, Mac OS 8.5 and Red Hat Linux. (Minor cosmetic problems still occuring.) Will formally mark as verified after checking 1.26.99 or later build on Win98.

Works on Win98; 1.26.99 build checked. (Okay, the links on the site don't work, but the behavior in the bug report is fixed. ;) Thus, verified.