Also, if you are using Windows Task Manager, be aware that the default column "Memory Usage" is often misleading. It shows the amount of physical memory used by the process. This can vary as the OS decides to page-in or page-out parts of your application. It is much more instructive to look at the "VM Size" column; this column is not shown by default but can be turned on in the View menu.
Betty Rubble? Well, I would go with Betty... but I'd be thinking of Wilma.
If you are using Java 5 or later, you can use jconsole to see where the VM uses how much memory.
In addition to the heap, there is also the permanent generation (basically the classes' byte code), the stacks (for local variables etc.), the VM itself etc. pp.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: I set Xmx to be 100M, but the java process