JVM - Microsoft JScript.dll Memory Leak when using Java Web Start
I have posted before a topic related to this matter, although now I have a lot more information about what is going on (although still no fix for it). This is the link to the earlier post, containing JVM HOTSPOT EXCEPTION_ACCESS_VIOLATION
http://forum.java.sun.com/thread.jspa?threadID=5116970&messageID=9402346#9402346
The issue is that after deploying on Windows XP a multi threaded, memory consuming (40 Mb) Java Swing application using Java Web Start, and the standard web page (IE6) reference to the jnlp file to launch the installation from Tomcat, each time this application gets executed by double clicking on the desktop icon (with no IE6 interaction at all), calls start being made between jvm.dll (sun) and jscript.dll (Microsoft IE), these interactions never release the memory they consume, so after a period of using the application it crashes unavoidably. If I execute exactly the same application launching it from command line (no Web Start nor IE6 browser involved), the application works nicely all the time, no problem at all.
My question is: does anyone know why these calls to jscript.dll are even being made during web start application execution? As said, it's a desktop Swing app, it does not need the browser at all, and jscript.dll is a IE dll. Anyone can advice on how these interactions can be eliminated?
I've worked with Microsoft support for two weeks on this issue and all they have said is that it is a Sun problem and they can not help further.
Thanks
Jes鷖
[1540 byte] By [
Castanona] at [2007-11-26 17:39:46]
# 2
Microsoft suggested (among others) two test.
1- Install IE7 and run the application
2-Install Firefox and run the application
Results were:
For 1: The application does not crash, apparently IE7 has a newer version of Jscript.dll that, in Microsoft words, handles better 'bad software', refering to 'bad software' to the java virtual machine I guess. Looking at the performance manager you can see memory goes down as with IE6, but at some point memory is released and the app. does not crash. Anyway is still is uncertain to me why Jscript.dll is getting involved at all. Although this solves the problem is not a viable solution for us, because I work in a corporation where changes such as upgrading the IE version on a large number of desktop can not be justified just because one app. is crashing, and it would take a long validation time anyway before the upgrade can proceed.
For 2: I did install Firefox in a machine and the application still crashed, but it is true I did not uninstall IE6, so the conflictive Jscript.dll was still sitting at system32. Quite possibly the crash would not happen if that dll wasn't there at all.
Thanks
Jes鷖
# 3
When Java Web Start is starting up, If the Control Panel has proxies set to "user browser settings", and the browser is set to "use proxy auto config script" (pac file) then Java Web Start will call the java script engine in IE (jscript.dll) to process the javascript in the pac file to determine the proxies.
A work around would be to use the Java Control Panel to set the proxy settings manually.
/Andy
