Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Fatal Plug-in Error with a different VM already loaded by another web page.

4 views
Skip to first unread message

Bob Rullo

unread,
Mar 4, 2003, 9:54:44 PM3/4/03
to
It appears that when you go from the 1.3.1 page and then go to the
1.4.1 plug-in based
page the 1.4.1 plugin attempts to hook onto the 1.3.1 VM. I would of
expected to see
a new 1.4.1 VM be started (with no errors, obviously).

Try this:
Test - Java Plug-in 1.3.1 to a Java Plug-in 1.4.1 page
Step 1 - Open a new browser window to
http://192.18.97.35/products/plugin/1.3/demos/applets/ArcTest/example1.html
Step 2 - In that same browser window go to
http://java.sun.com/products/plugin/1.4.1/demos/plugin/applets/ArcTest/example1.html

You'll receive the following error:
Title: "Java(TM) Plug-in Fatal Error"
Message: "Attachment to a running Virtual Machine failed"


To further show the errors that occur when trying to load multiple
plug-in VMs try the reverse.
Test - Java Plug-in 1.4.1 to a Java Plug-in 1.3.1 page
Step 1 - Open the 1.4.1 url in a new browser window.
(http://java.sun.com/products/plugin/1.4.1/demos/plugin/applets/ArcTest/example1.html)
Step 2 - Now, in the same window, navigate to the 1.3.1 site.
(http://192.18.97.35/products/plugin/1.3/demos/applets/ArcTest/example1.html)

You'll receive another error message this one appearing to be uglier
than before.
Title: "Microsoft Visual C++ Runtime Library"
Message: "Runtime Error!
Program: C:\Program Files\Internet Explorer\iexplore.exe

abnormal program termination."


Key things to note:
Browsers: IE 5.5,
6.0 (6.0.2800.1106.xpsp1.020828-1920IC)
Netscape 6.2+ (not personally verified but reported by a
client)

OS: Win2K, WinXP

Bob Rullo

unread,
Mar 5, 2003, 10:47:20 AM3/5/03
to
Sorry, forgot to post my questions for this defect.

Has anyone seen this before? Do you know of a workaround that will
ensure that a new VM is initated from within one browser process?

I've tried launching another window via javascript and housing the
applet there, but had the same error occur. It appears that
window.open in JS doesn't create a separate browswer process and
leaves me in the same situation as before.

Would greatly appreciate any feedback..

Thanks
-Bob

Bob Rullo

unread,
Mar 19, 2003, 3:03:49 PM3/19/03
to
I was also able to reproduce this on Windows 95 as well as Netscape 6.2.1
-Bob


rru...@yahoo.com (Bob Rullo) wrote in message news:<e294a2ad.03030...@posting.google.com>...

0 new messages