dont have any problem....never had
3 GB memory clean installation, no other software running on that pc, stable Internet connection... thats it--- and always latest version of TWS AND JAVA
I get freeze-ups and I suspect RAM starvation as well. It mostly happens when I open another TWS window and then close it. For instance, if I open the account window or a chart and then close it.
I haven't seen any IB issues this morning. You should also check the java parameters you are using to call TWS. I recently found that I did not have enough memory allocated to each TWS window. The relevant parameter is
"-Xmx512M" which allocates up to 512mb to each window. This should be adequate. My TWS performance and stability improved dramatically after that change.
no freeze-ups. Running TWS on dedicated machine with NT frontend tho so my TWS windows are limited. Using 3meg on XP system. JAVA sucks in this regard because it tends to not release the memory when window is closed.
I get freeze-ups and I suspect RAM starvation as well. It mostly happens when I open another TWS window and then close it. For instance, if I open the account window or a chart and then close it.
no freeze-ups. Running TWS on dedicated machine with NT frontend tho so my TWS windows are limited. Using 3meg on XP system. JAVA sucks in this regard because it tends to not release the memory when window is closed.