On May 22, 2011, at 2:52 PM, Casper Bang wrote: > You should probably have forked a new discussion of this. Anyway, I > don't claim to understand the intricate detail of what exactly causes > memory to leak through classloaders and PermGen space to skyrocket. I > just know that is *IS* a real problem that one can not redeploy and > app to an application container, without the risk of having the JVM > crash (usually silently), with all applications hanging > unresponsively! > > Oddly enough, it's not a concept known in the Android or Mono world.
Mono/C#/Dalvik VMs have different classloading models > Are you saying then that, even with the PermGen removed in JDK7, we'll > still suffer the same problems just manifested in different ways? And > if so, in which ways? Yup, and it is the fault of the classloading model, not the JVM. If you load an application enough times you will run out of memory. Before that you'll experience a new effect of increased GC pause times, more frequent CMS failures reverting to full STW GC's which will eventually lead to the infamous OOME. Regards, Kirk -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
