This week's book giveaway is in the Cloud/Virtualization forum.
We're giving away four copies of Learning OpenStack Networking: Build a solid foundation in virtual networking technologies for OpenStack-based clouds and have James Denton on-line!
See this thread for details.
Win a copy of Learning OpenStack Networking: Build a solid foundation in virtual networking technologies for OpenStack-based clouds this week in the Cloud/Virtualization forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Knute Snortum
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Ganesh Patekar
  • Stephan van Hulst
  • Pete Letkeman
  • Carey Brown
Bartenders:
  • Tim Holloway
  • Ron McLeod
  • Vijitha Kumara

Java Pluggin parameters... and crash  RSS feed

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,
We have an application that uses Applets to perform cryptography.
Those applets are stored on the client machine.
We use Java Plug-In 1.4.2, Windows XP and IE(any version From 5.5).
To be sure the Application can crypt huge files we need to set the Java mememory to 512.
So we add a line to the deployment.properties
javaplugin.jre.params=-Xmx512m
(this line is automaticaly added when you specify the -Xmx512m parameter with the Plugin configuration tool)
But it appears that on some machines when you try to load any Applet ( on any website with applet) the IE browser closes without any warning.
When you change the line and set the memory to 256, it works fine...
Now the question: Why? When we used those applets on other platforms they always worked, and they work on many Windows XP machines too...
Have someone had the same bug?
Is this a "well-known" bug?
Thanks.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!