How does Hotspot Java/JVM store memory?

Question

Is there anywhere that a hostspot JVM process stores memory besides these places:

• perm gen
• tenured generation
• eden space
• from space
• to space
• code cache

That is to say: What possible ways are there that the hotspot process can reserve & commit memory on a machine such that said memory would not show up in the statistics for one of those places?

Some answers I can think of (let me know if these are true):

• virtual memory used for thread stacks are not represented in those numbers
• any loaded dlls or files.

EDIT:

some other answers given:

• java.exe itself
• JNI methods could allocate memory itself
• any native code (eg. from dlls) could allocate memory.
• general JVM metadata for running itself.

Answer 1

You're correct so far (DLLs include all JNI libraries and whatever memory they've allocated). The VM also has its own code (e.g., the contents of java), bookkeeping information about the memory that's allocated to Java programs, and potentially memory used by VM agents. Basically, what you described in your first list are the items that make up the "running memory" of the virtual machine; the rest of the JVM's memory are all of the items that represent the virtual machine's "hardware", such as the libraries that connect it to the OS's networking, graphics, and so on.