Closed Bug 4474 Opened 26 years ago Closed 26 years ago

Apprunner and viewer crash on launch with "invalid NT image" for plugins

Categories

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

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: dgabol, Assigned: amusil)

Details

Windows NT Server 4, service pack 4. Nothing else running apart from a few taskbar utilities. Machine Dell XPSR 450 128 Mb RAM. Netscape Communicator 4.5 installed on machine as well. The version of Mozilla that I was testing was downloaded from your FTP site from the "latest" directory, timestamp on directory was Wed March 31 13:59:00. Start apprunner or viewer.exe. The DOS box gets as far as saying composer has been bootstrapped. Then I get three windows error dialogs one after the other. The first two give the path to my Communicator plugin directory and then say npaudio and npavi are not valid Windows NT images. The final one says initialisation of dynamic link library npjava11.dll failed. I then get one of those lovely Dr.Watson dialogs which informs me the program is terminating abnormally....... then it terminates abnormally. Microsoft got something right :-) Looking at the dll I'd guess the problem is to do with lack of java support in Mozilla but I'll leave it to you guys to tell me if that's right or not! Seeyah g'luck, Dave.
Severity: normal → critical
Just to let you know this still happens with the latest build from Monday April 5th.
Assignee: don → amusil
Component: Apprunner → Plug-ins
Status: NEW → ASSIGNED
I checked in a fix for this last week. What are the names of the dlls you're getting errors on?
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
There is a problem with the publically available JRE and plugin from Sun with Seamonkey. The plugin shipped with that package crashes the browser and there is no way around it unless you remove the plugin.
Hi, I've been off sick and have just returned, that's why I didn't answer your DLL query. I see the bug is resolved "fixed". Does that mean you have supplied a fix or that the JRE will forever crash the browser and that is seen as a fix? Or that you are working on a fix? Thanks, Dave.
QA Contact: 3853 → 3849
beppe, I don't have NT. Could you Verify please?
Hi, With the new JDK121 and JRE121 installed this no longer happens. As far as I am concerned you can close this but you may decide otherwise for backwards compatibility.
beppe, you want to mark this one Verified now? :-)
Target Milestone: M6
Status: RESOLVED → VERIFIED
marking verified
URL: N/A
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.