Hi joel, thanks for the info. Investigating native memory issues is on our agenda, but for now we were suspecting the metro library to be leaking memory. Do you use process queue in combination with web services?
The native memory is an extra piece outside of the JVM, that is visualized in the graphs of the Mendixcloud. The memory is mostly used by Java threads. Each Java thread takes a piece of extra memory beside the JVM in the native memory. That piece has a default value and when a thread is ended it release to be reused for a new thread. In the graph you see that the native memory is stabilizing along the way.
I've seen an interesting page what explains the native memory: http://www.ibm.com/developerworks/linux/library/j-nativememory-linux/index.html
My deeper question is: why is the uses of the native memory a lot more when I use the process queue in an app vs when I don't use it? Even when the process queue isn't implemented in the application to be used so there aren't any threads triggered by the process queue.
I have had similar (or even worse actually) experiences with the process queue module as well. I am pretty sure one of the problems at least is the way Mendix handles system sessions. I do not have any hard evidence that Mendix is still leaking memory for system sessions but it did so in the past.
I also have had similar an experience.
Hasn't this issue been settled yet?