Both you (@Matthias) and Mark Murphy (@CommonsWare) are correct in what you say, but the gist seems lost. (The use of volatile is correct and classes are not unloaded.) The crux of the question is where initialize is called from. Here is what I think is happening: You are calling initialize from an Activity * … Read more
Your heap is full GC_CONCURRENT freed <1K, 14% free 21220K/24455K, paused 6ms+26ms GC_CONCURRENT : Jumps in because Heap is full 14% free 21220K/24455K After this collection 14% of memory is free. Check the heap usage. paused 6ms+26ms Time taken to collect garbage. Obviously there is a huge memory leak in your code that you have … Read more
It’s not explained very well, but as far as I can tell, the server mode is synchronous per core, while the workstation mode is asynchronous. In other words, the workstation mode is intended for a small number of long running applications that need consistent performance. The garbage collection tries to “stay out of the way” … Read more
When implementing the dispose pattern you might also add a finalizer to your class that calls Dispose(). This is to make sure that Dispose() always gets called, even if a client forgets to call it. To prevent the dispose method from running twice (in case the object already has been disposed) you add GC.SuppressFinalize(this);. The … Read more
Is it possible to nevertheless loop over entries in some way? No, as you say, the contents of a WeakMap are not accessible by design, and there is no iterability. If not … how does the Chrome console do this? The console uses the debugging API of the JS engine, which allows access to the … Read more
It may be relevant that Perl never gives memory back to the system by itself: It’s all up to malloc() and all the rules associated with that. Knowing how malloc() allocates memory is important to answering the greater question, and it varies from system to system, but in general most malloc() implementations are optimized for … Read more
Here are some articles detailing problems with the Large Object Heap. It sounds like what you might be running into. http://connect.microsoft.com/VisualStudio/feedback/details/521147/large-object-heap-fragmentation-causes-outofmemoryexception Dangers of the large object heap: http://www.simple-talk.com/dotnet/.net-framework/the-dangers-of-the-large-object-heap/ Here is a link on how to collect data on the Large Object Heap (LOH): http://msdn.microsoft.com/en-us/magazine/cc534993.aspx According to this, it seems there is no way to compact … Read more
The first thing about CMS that I have learned is it needs more memory than the other collectors, about 25 to 50% more is a good starting point. This helps you avoid fragmentation, since CMS does not do any compaction like the stop the world collectors would. Second, do things that help the garbage collector; … Read more
If your application is not interactive, and GC pauses are not an issue for you, there shouldn’t be any problem for 64-bit Java to handle very large heaps, even in hundreds of GBs. We also haven’t noticed any stability issues on either Windows or Linux. However, when you need to keep GC pauses low, things … Read more
Default garbage collectors: Java 7 – Parallel GC Java 8 – Parallel GC Java 9 – G1 GC Java 10 – G1 GC