Fwd: GC overhead limit exceeded
tal.liron at threecrickets.com
Wed Mar 5 22:28:28 PST 2014
Well, I've reached the limits of my personal knowledge to work on this
problem. I'm happy to assist in any way I can, including providing
access to servers.
As it stands, however, it seems that this problem will follow through
into the official release of OpenJDK 8, which means that I won't be able
to recommend Nashorn for production deployments of Prudence. Perhaps
there will be a fix later on?
(By the way, there is no bug with Log4j 2.0 -- the high number of
instances is by design, an effect of using the innovative Disruptor
library for inter-thread communication.)
On 02/25/2014 02:12 AM, Tal Liron wrote:
> I've been away for a month. Has anyone with knowhow followed up on this?
> The issue is still present.
> On 01/18/2014 02:51 PM, Tal Liron wrote:
>> I have a new dump that will hopefully be more useful:
>> From what I can tell, indeed lambda forms are way out of control
>> here. Generally, too, there is a huge amount of Nashorn-related
>> instances, which may be related.
>> (Note that Log4j 2.0 also seems to be having a serious memory leak! I
>> have opened a bug about it over there.)
More information about the nashorn-dev