> My take on the garbage collection issue would be to (if it were > possible) have all the garbage collection done at night, or > perhaps on the weekends when I'm doing other stuff. What do I > care if the cursor seizes up, if I'm at the beach at the time.
I'm sorry, but to be frank it's obvious you don't understand garbage collection at all. It has to happen or you run out of memory. That's java for you. The garbage collector scans every object that has been created in your VM and looks to see if there are any more references to it in any code that is active. If not, it will free the memory used by that object. If you wait until 128MB of RAM is used before garbage collecting, there is potentially a lot more work to be done before collection is complete. Some garbage collection implementations need to lock the whole memory allocation system in order to maintain heap integrity � hence the total lockup for you. When garbage collection happens, it's because it needs to � you are running out of RAM allocated to the VM, so it tries to recycle some. Depending on your VM settings it may also then allocate some more memory from the underlying O/S if it still needs it. I suggest you read a book on Java memory management. You need to understand this if you want to write java applications that perform well. Marc _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-features
