Mozilla crashes whether I run apprunner.exe or viewer.exe For apprunner: APPRUNNER caused an invalid page fault in module COOKIE.DLL at 0137:600c1bd1. Registers: EAX=80040154 CS=0137 EIP=600c1bd1 EFLGS=00010206 EBX=600c7154 SS=013f ESP=0063fbb0 EBP=0063fbdc ECX=0063fbd8 DS=013f ESI=00000000 FS=10ef EDX=815c0440 ES=013f EDI=80000000 GS=0000 Bytes at CS:EIP: 8b 06 53 56 ff 50 48 85 c7 74 04 6a 00 eb 03 ff Stack dump: 0063fbd8 007ccf90 00000000 80000000 dc26e0e0 11d1ca94 8000a4a9 c47a8a5f 00000000 600c123e 00000000 0063fc20 600c1249 0063fccc 007ccf60 007609f0 Then, for viewer: VIEWER caused an invalid page fault in module VIEWER.EXE at 0137:00409ac5. Registers: EAX=0064fd80 CS=0137 EIP=00409ac5 EFLGS=00010246 EBX=00540000 SS=013f ESP=0064fb58 EBP=0064fd88 ECX=00000000 DS=013f ESI=00000000 FS=10ef EDX=815c0000 ES=013f EDI=00000000 GS=0000 Bytes at CS:EIP: 8b 46 08 85 c0 74 06 8b 08 50 ff 51 04 8b 4c 24 Stack dump: 007b3530 00407979 0064fd80 00000000 00540000 815c0430 00000000 172705b6 00240000 00029558 00000000 00000828 00000000 ffff0000 00000000 8bc20000 I'm not sure that this happens to other people, so I'll rather mark it as Critical than Blocker.
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → INVALID
jasonfilby, sorry, but this bug does not contain enough information for an engineer to investigate as submitted. Please re-open or re-submit with the information contained in the Mozilla Bug Writing Guidelines, at http://www.mozilla.org/quality/bug-writing-guidelines. Finally, have you already read the Release Notes (http://www.mozilla.org/ projects/seamonkey/release-notes/m10.html) and followed the "READ THIS Before You Install" section? Thanks!
What more could you possibly want? I'm trying to run Mozilla on Win95 and both apprunner.exe and viewer.exe crash on execution -- I also provided the crash data that Windows threw back at me. I don't have any more info to give, unless there's some specific test you want me to run.
More information: - Old mozregistry.dat exists when M10 is first run - Problems occur and then mozregistry.dat is deleted - More problems, that are resolved by deleting component.reg and then rerunning M10 - Obviously the old mozregistry.dat affected the way component.reg was built So all bugs related to this one where caused because mozregistry.dat was not deleted before running M10 -- and deleting it afterwards ghosts this bug. Enough info? You can mark bug 16187 as closed too..
You need to log in before you can comment on or make changes to this bug.