Closed Bug 6195 Opened 26 years ago Closed 26 years ago

Apprunner crashes on startup under NT 4.0 SP5

Categories

(Core Graveyard :: Tracking, defect, P2)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: rbonner, Assigned: law)

Details

I get the following on the command line after starting apprunner: nsComponentManager: Using components dir: E:\test\mozilla\x86rel\components width was not set height was not set defaultReading file... Reading file...Done The Messenger component is available. Initializing... Messenger has been bootstrapped! The Composer component is available. Initializing... Composer has been bootstrapped! Reading file... Reading file...Done Reading file... Reading file...Done Then I see a partially drawn window and then a dialog box w/ the title: ToolTipText: apprunner.exe - Application error And the following in the dialog box: The instruction at "0x503317b0" referenced memory at "0x017161c8". The memory could not be "written". Click OK to terminate the application. Click on CANCEL to debug the application. I tried several times but the application would not start even after rebooting with no other apps were running.
Assignee: don → law
Severity: blocker → critical
Priority: P3 → P2
Target Milestone: M6
Bill, can you figure out what's going on here?
QA Contact: 3853 → 3849
Updating QA Contact
More infor per email from rbonner: I found the origin of the problem. I went in to the VC++ debugger (a brave move for me... I've been almost exclusively Java/Perl for the last 3 years :o) and it reported: Unhandled Exception in apprunner.exe (NPJAVA32.DLL); 0xC0000005: Access Violation. So I tried swapping out the NPJAVA32.DLL in \Netscape\Communicator\Plugins with the NPJAVA32.DLL from Sun's JDK 1.1.8 instead of the JDK 1.2.1 DLL and Mozilla came up. Should the Java 2 plug in work?
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → INVALID
This is a dup of another bug (which I can't for the life of me figure out the number of, so I'm marking this one invalid). There is a known problem with the java plugin. Another workaround is to create an empty plugins directory where your apprunner sits.
Status: RESOLVED → VERIFIED
I can't find bug either...marking Verified.
Moving all Apprunner bugs past and present to Other component temporarily whilst don and I set correct component. Apprunner component will be deleted/retired shortly.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.