Closed Bug 16187 Opened 25 years ago Closed 25 years ago

Apprunner loading causes invalid page fault in XPCOM.

Categories

(Core :: XPCOM, defect, P3)

x86
Windows 98
defect

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: mnegandhi, Assigned: dp)

Details

Attachments

(1 file)

This error occurs everytime I try to start up Apprunner . APPRUNNER caused an invalid page fault in module XPCOM.DLL at 015f:60ad1510. Registers: EAX=00000000 CS=015f EIP=60ad1510 EFLGS=00010216 EBX=00c33010 SS=0167 ESP=0063eeb8 EBP=0063efc0 ECX=000000a1 DS=0167 ESI=0063eff0 FS=645f EDX=817e5048 ES=0167 EDI=0063efec GS=0000 Bytes at CS:EIP: 80 38 00 74 08 50 8b ce e8 1e fa ff ff 5e c9 c3 Stack dump: 0063eff0 00000100 0000010c bff7b9b6 817e2ff8 0000010c 780012b1 0000003f 00000100 0000010c bff7b9b6 0000003f 0063ef84 011c5870 bff7b9b6 817e2ff8 After a few more attempts I got this error instead : APPRUNNER caused an invalid page fault in module COOKIE.DLL at 015f:600c1bd1. Registers: EAX=80040154 CS=015f EIP=600c1bd1 EFLGS=00010206 EBX=600c7154 SS=0167 ESP=0063fbb0 EBP=0063fbdc ECX=0063fbd8 DS=0167 ESI=00000000 FS=6227 EDX=817defcc ES=0167 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 007ec760 00000000 80000000 dc26e0e0 11d1ca94 8000a4a9 c47a8a5f 00000000 600c123e 00000000 0063fc20 600c1249 0063fccc 007ec8b0 00760350
Target Milestone: M10
Could you try removing the file mozregistry.dat before restart. This should be in your C:\WINNT directory.
Tried that . Got this error ( before and after rebooting ) : APPRUNNER caused an invalid page fault in module COOKIE.DLL at 015f:600c1bd1. Registers: EAX=80040154 CS=015f EIP=600c1bd1 EFLGS=00010206 EBX=600c7154 SS=0167 ESP=0063fbb0 EBP=0063fbdc ECX=0063fbd8 DS=0167 ESI=00000000 FS=0fa7 EDX=817ad8ac ES=0167 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 007ebd20 00000000 80000000 dc26e0e0 11d1ca94 8000a4a9 c47a8a5f 00000000 600c123e 00000000 0063fc20 600c1249 0063fccc 007ea4c0 00760350
Target Milestone: M10 → M11
Ok. Now that we have eliminated that possibility, can you say which build you are running. Since you cant start, you wont be able to read the build number off the screen. So could you let us know how you got this build.
Thanks. So that is the M10 build. Before we try more debugging, I want to eliminate highlevel problems. Did you install the build on top of an old build ? After you deleted mozregistry.dat and ran, was one created for you ? (reboot is not required). Again, mnegandhi, thanks for all the information and working with us in finding the problem.
I did have M9 previously installed . I had removed that several weeks ago . Installation was in a fresh directory . Initially some process message would show up as normal in the DOS window , and then it would fail with Invalid app message . Now it just goes to DOS mode and fails immediately . The file is being recreated everytime I try to run Apprunner . My machine config is PIII 400 MHz w 128MB of RAM & Win98 ( dual booting with WinNT 4 , although I am running this only in Win98 yet ) .
Ok I believe we have a real bug. Could you do this. In the dos command prompt type: set NSPR_LOG_MODULES=nsComponentManager:5 set NSPR_LOG_FILE=xpcom.log cd <the directory that contains apprunner.exe> apprunner This should create a file called xpcom.log Could you add the file as an attachment.
Attached file Log file (deleted) —
0[761990]: nsComponentManager: FindFactory({dc26e0e0-ca94-11d1-a9a4-00805f8a7ac4}) 0[761990]: found xppref32.dll as 775ba0 in factory cache. 0[761990]: CreateInstance() FAILED. This is your problem. xppref32.dll should not exist in your build. Are you sure you did a fresh install of M10 as opposed to installing M10 build on top the M9 build ? Could you search for xppref32.dll in your mozilla installation directory. Also, search for *pref* under the mozilla installation directory. There should be one under components/ directory.
xppref32.dll does exist in the \bin\components directory in the mozilla installation directory . I had done the install into a new directory . And the file is included in the release ( just checked the zip file contents for that ) . Although checking through the rest of disk , I noticed that there is a copy of the dll in the Netscape 4.7 install on my m/c .
Status: NEW → ASSIGNED
What is reported is a proper clean installation. I am sold. So why does your installation think that it has that object in xppref32.dll and not in rel:xppref32.dll We changed this from M9 to M10. Let us try this: - delete bin\component.reg - delete xpcom.log - set variables as recommended in my previous add to the bug - run apprunner again from commandline - attach the xpcom.log This should work. Else we will be closer to the problem. Ccing neeti, owner of prefs.
BTW, mnegandhi, thanks for all your quick responses and your interest in mozilla. It is a pleasure to work with you.
Umm in addition to your instructions , I deleted the file (xppref32.dll) from my Netscape 4.7 install , so there is only the one copy ( in \bin\components of the mozilla install ). It started up with the preference window , and the browser normally this time . Do you still want the log file ?
Naa if it works, I wont need the log. Somehow your component.reg wasn't upto date (beats me). I dont think the nav4.7 xppref32.dll mattered. Shall we close this bug report.
Actually the component.reg which came in the zip , and the one on my machine are different ( don't know why ) . And it fails consistently with that .
I see. If you replace the component.reg that you generate with the one in the package, you fail right ? That is a serious problem. Can you confirm that for sure. thanks.
Sorry , I reinstalled the whole package and now it seems to be working fine . Not reproducible any more . Anyhow I'm heading off for the night ( gettin glsightly late here on the e. coast ) . I'll be glad to let ou know if I encounter the error again .
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Verified
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: