JDK-6627835 : Need a way to force an applet into its own JVM instance
- Type: Enhancement
- Component: deploy
- Sub-Component: plugin
- Affected Version: 6u10
- Priority: P3
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2007-11-09
- Updated: 2010-09-08
- Resolved: 2008-06-13
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 6 | JDK 7 |
|---|---|
6u10 b13Fixed  |
7Fixed |
Related Reports
|
Relates :
|
Description
In a discussion with a customer about the new Java Plug-In, a mechanism for forcing an individual applet into its own JVM instance was requested. While specifying JVM command-line arguments such as -Xmx will increase the chances of an applet getting its own JVM instance, there might be situations where a given applet really doesn't want to run in the same JVM with any others. This is a simple change to make so we should try to support it in the initial release.
Comments
|