JDK-4947162 : CAxControl::OnJSInvokeMethod() - Access violation potential
  • Type: Bug
  • Status: Closed
  • Resolution: Fixed
  • Component: deploy
  • Sub-Component: plugin
  • Priority: P2
  • Affected Version: 1.2.2,1.4.2_12,5.0
  • OS: windows_nt,windows_2000,windows_xp
  • CPU: x86
  • Submit Date: 2003-10-31
  • Updated Date: 2006-11-21
  • Resolved Date: 2003-11-24
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 Availabitlity Release.

To download the current JDK release, click here.
Other
1.4.2_14Resolved
Related Reports
Duplicate :  
Duplicate :  
Description
The applet in http://www.apl.jhu.edu/~hall/CWP-Sources/CWP-Examples/Chapter19/Everest.html is doing java to javascript communication. To reproduce the problem:
* Go to that page
* Point to the applet, scroll the bottom scroll bar quick
* Hit the reload or "back" button

Expected vs. Actual behavior:
Expected:
Browser should not crash.

Actual:
The browser crashes
###@###.### 2003-10-31

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger-beta FIXED IN: tiger-beta INTEGRATED IN: tiger-b30 tiger-b32 tiger-beta VERIFIED IN: tiger-beta
2004-06-14

EVALUATION When the page is switched or reloaded while there is a request to Java->JS call, the JNI code releases the JNI references and returns without waiting for the call to complete. Releasing memory is fine as long as the Java->JS call is in action. But if the call is yet to start, plugin could be using the already released JNI references in which case the browser crashes ###@###.### 2003-11-07
2003-11-07