Thu Nov 12 16:07:00 GMT 2015 memoryIt won't happened at java, but for non-GC language like C++, crash at constructor will cause memory leak: http://blogs.asman-it.com.au[..]oders-have-it-easy-crashing-constructors Discussion of if there are way to recover OOME - http://dobbscodetalk.com[..]-a-Non-Recoverable-Error-.html&Itemid=29 http://blog.maxindelicato.com[..]ghly-available-inmemory-shard-index.html Discussion about using memory as store - http://martinfowler.com/bliki/MemoryImage.html When using direct memory can be faster, when you have a large amounts of data and/or you have to perform some IO with that data. Tick data is a good example - http://vanillajava.blogspot.com.au[..]n-using-direct-memory-can-be-faster.html http://www.memorymanagement.org/index.html (google search) (amazon search) second |