From: Miguel <mi...@jm...> - 2005-08-30 21:15:09
|
>>Note that I was not able to run this on my linux box ... out of memory.= >>I am able to run it on my Win32 box. >> >>The JVMs have *approximately* the same about of memory available on all= >>platforms, so it seems that this file is right at the limit. >> >>Therefore, I suggest you be careful when showing it off because it migh= t >>fail on some platforms. > > How gracefully (or not) does java handle such an out-of-memory conditio= n > on linux? On Windows or Mac? Not graceful It is conceivable that I could catch the error condition and recover a little more gracefully ... but I think that work would be low priority. If it hurts when you try to pick up a big molecule, then don't do it ... > I'm happy to warn people but I don't want to frighten them if the handl= ing > is graceful. > > How much total memory do you have on your linux box? It is not a question of how much physical memory you have in your machine= . When the Java Virtual Machine starts it allocates a maximum amount of memory to use. This amount of memory is fixed and is completely independent of the amount of physical memory that you have in your machine. I searched on the web for a few minutes, but could not easily locate anything that was definitive. I thought that the number was 96 Mb. But I only found one reference on te= web (some random article, not from Sun) that said 64 Mb. One can change the default heap size for the Java Plug-in, but the proces= s is not pretty. There is no way to try to have the applet increase the memory size. Miguel |