Question

This is a follow-up question to How are static arrays stored in Java memory? .

So global variables in C/C++ are stored in the static data segment of memory. But what about static class variables in Java/C++?

It can’t be the static data segment because you don’t know what/how many classes are going to be referenced throughout the duration of your program (because of reflection). It’s definitely not the stack because that makes no sense. Storing it on the heap is also kind of iffy.

Answer 1

In Java, at a low level, class static variables are indeed stored on the heap, along with all other class metadata. To Java, they look like globals, but to the JVM’s low level heap management routines, they’re dynamic data (although they may be treated slightly specially in order to improve GC efficiency, since they’re likely to be long lived). After all, classes can be unloaded by unreferencing their classloader.

As for whether it’s the same as the C malloc(), not likely. Most JVMs take control of their heaps at a low level; they grab a chunk of memory from the OS and divvy it up themselves. As such, most Java data, including static data, are not stored in the malloc heap, but rather in a separate heap managed by the JVM.