Hi,
I'm wondering how the xmx memory is allocated on Windows systems. Does anyone know?
I have the problem that using the JNI interface I can access a driver dll only when the xmx value is below ~200M, otherwise the driver produces an error. Now I will make a C++ application to test if I can reproduce the behaviour.
Thanks
Mario
Sun's JVM (HotSpot) uses VirtualAlloc() to first reserve a contiguous range of virtual addresses for the java heap. Eliding lots of details, some memory is committed in this virtual range at initialization (basically the -Xms value) and more is committed as needed when the java heap expands.
I think a better place to start would be what type of error you are seeing from the dll? Since it seems sensitive to available memory (or available address space), does the dll require lots of memory?
