jdubster

Thanks Obinna, that would be great if you can check back on this issue after the next release. Any guidance you may have on the release schedule would also be appreciated. I'm running SC version 2.863 on os x 10.6.8. I'm looking at the jvm using the "jconsole" memory profiler, and I can see that the "CMS Old Gen" memory pool just keeps increasing. The other memory pools look normal. One thing that seems to help in addition to the "-Xmx1000m" flag on the command line is to add a "-d32" flag. This forces the 1.6 jvm to run in 32 bit mode. It doesn't fix the memory leak, but the initial heap size is smaller, so SC may run for longer before overflowing the heap.

This is kinda of a big deal for us as well, it used to be that SuperContainer was more stable even that Filemaker Server. Now it has been crashing every week. Also, once SC crashes it prevents any scheduled reboots. On 10.6, the recommendation to target the java 5 jvm like so: /System/Library/Frameworks/JavaVM.framework/Versions/1.5/Commands/java has no effect; the path just points to the java 6 jvm anyway. It seems like this is a memory leak that was introduced by a java update. Is there anyone at 360works who would take a look at a Heap Dump if provided?