Home/ Questions/Q 270069
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T23:56:25+00:00

How can I determine the address in memory of the Java heap for a

  • 0

How can I determine the address in memory of the Java heap for a JVM running in the current process? That is, get a void* pointer or equivalent to the contiguous area of memory that the JVM has allocated for the heap, using Java, C, or other calls?

Matlab has a JVM embedded in its process. The memory the JVM allocates is unavailable for Matlab arrays, and of this, the heap is important, because it takes a big contiguous chunk of memory and never shrinks, and Matlab also needs contiguous memory for its arrays. If the heap is reallocated during expansion, that could cause fragmentation.

I’d like to instrument my process to examine the interaction between the Java heap and Matlab’s view of memory, and to find out when it moves due to resizing, preferably all from within the process. This needs the address of the heap. It’s easy to find the heap size from java.lang.Runtime, but not its address in memory. How can this be done?

I’m running Sun’s JRE 1.6.0_04 in a Matlab R2008b process on Windows XP and Server 2003. I realize this probably needs to be a vendor-specific technique. The process runs code we’ve written, so we can use custom Java, Matlab, JNI, and C/C++ code. Java method calls or supported hooks in the JVM would be preferred to low-level hackery.

EDIT: The goal of this is to examine the interaction between the JVM’s GC and Matlab’s GC. I have no need to see into the Java heap and won’t be reading anything from that memory; I just want to see where it is in the context of the overall virtual memory space that Matlab’s GC is also trying to fit data into.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    A quick ‘n dirty way to get the actual heap address of the JVM is to jump into WinDbg, attaching to the JVM and issue a single !address command. Somewhere around 0x2??????? (It differes between jvm versions but remains static for that version) will be a large VAD marked PAGE_EXECUTE_READWRITE, this is your JVM’s heap in the process’s memory.

    To confirm, you can set a breakpoint on kernel32!VirtualAlloc and upon JVM initilization in the module JVM.DLL you will hit on the call to VirtualAlloc showing you the jvm allocation its heap. If you check out the code around this call you can see how the address is calculated.

    • 0