Closed Bug 433 Opened 27 years ago Closed 26 years ago

Page fault error created when Netscape launched before Windows completes loading

Categories

(Core Graveyard :: Plug-ins, defect, P3)

x86
Windows 95
defect

Tracking

(Not tracked)

VERIFIED WONTFIX

People

(Reporter: jccampb, Assigned: don)

Details

Created by Jean Campbell (jccampb@mitre.org) on Tuesday, June 9, 1998 11:41:42 AM PDT Additional Details : Even when Windows 95 indicates that it is ready to launch applications (i.e., the hour-glass turns to arrow), if insufficient time has passed before launching Netscape, the following error will be generated every time: "This program has performed an illegal operation and will be shut down. If the problem persists, contact the program vendor. NETSCAPE caused an invalid page fault in module KERNEL32.DLL at 0137:bff780f4." The version of Netscape being used is Navigator Gold 3.01. Updated by Patrick Pollet (Patrick.pollet@insa-lyon.fr) on Thursday, July 2, 1998 9:51:11 AM PDT Additional Details : Hi, Never had it with Netscape 3.01 Gold. BUT I am getting a similar problem with communicator 4.05 Fr and the new release (4.05 english with JDK 1.1 support). Communicator is installed in a Netware file server and is launched by Netware Application Launcher . Makes no difference actually. I get the same when double-clicking on the EXE file. This GPF happens BEFORE the splash screen shows up. Thus it is not a problem of cache or bad netscape.hst or bad user prefs as I have red in NUGIES. If I just ignore the Windows dialog Box , Communicator DO load and run properly. I can then close the GPF dialog box,after Communictaor is fully loaded, and it keeps running ... and is functionnal... It looks like a GPF in a "side thread" launched at startup. I did try to use a lower screen resolution (down to 640*349 * 16 colors) since I initially though it was a problem with the video drivers (S2 trio V3), but no difference. This error only happens the first time a user launch Communicator after logging in. The second run is OK... but if we stops the PC or simply logout-login, we get the very same GPF at the first run !!! It tried Dr Watson, but I never got any message. I tried to launch a DLL spy program, but I never found any extra DLL in memory whether I got or not the GPF... I noticed that the mouse cursor always stays as "hour glass" ,until I press the mouse button, whether I get or not the GPF. If I simply copy the Communicator directory on the local disk (or install it there), I never get the problem... Looks like Windows is " getting impatient" about Communicator showing up and try to kill it ... why ? Here is what I get on a 16Mb RAM PC ( win 95B, with kernel update and service pack 1). Never had any problem on machines with 32 Mb of RAM , whatever Windows version we are using... NETSCAPE a causé une exception c0000006H dans le module KERNEL32.DLL à 0137:bff95db6. Registres : EAX=c00197e4 CS=0137 EIP=bff95db6 EFLGS=00000202 EBX=6000e180 SS=013f ESP=0117fd9c EBP=0117ff80 ECX=c00197e8 DS=013f ESI=81567ee0 FS=406f EDX=00000044 ES=013f EDI=815647b8 GS=0000 Octets à CS : EIP : 8b 73 04 8b 43 10 2b 33 8b 11 03 c6 50 ff 72 18 Etat de la pile : 00000008 815647b8 81567ee0 81567ee0 bff95ebc 81567ee0 6000e180 815647b8 81567ee0 bff7b942 81564b18 6000e180 00000002 00000001 81564b18 00000040 sometimes I get this one: NETSCAPE a causé une exception c0000006H dans le module JRT3240.DLL à 0137:600a8240. Registres : EAX=600a8240 CS=0137 EIP=600a8240 EFLGS=00000a82 EBX=81563834 SS=013f ESP=0128fdb8 EBP=0128ff80 ECX=c420405c DS=013f ESI=81563878 FS=4127 EDX=c00197ec ES=013f EDI=60070000 GS=0000 Octets à CS : EIP : 53 b8 01 00 00 00 8b 5c 24 0c 56 57 85 db 55 75 Etat de la pile : bff7b9b5 60070000 00000002 00000000 60070000 81563878 81563834 81560f4c 00000040 81563834 c420405c c420405c bff78028 bff62482 01287000 bff7bab0
Reassing Marc Byrd's mozilla bugs to Jean-Charles for proper routing.
Assignee: mourey → don
WinFE bug? Reassigning to don@netscape.com
WinFE bug? Reassigning to don@netscape.com
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → WONTFIX
Status: RESOLVED → VERIFIED
Old bug, old code base. Marking won't fix.
Moving this bug to NGLayout Plug-Ins component in prep for move to Browser Plug-Ins Component
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.