public inbox for [email protected]  

help / color / mirror / Atom feed

From: Chapman Flack <[email protected]>
To: Kartik Ohri <[email protected]>
Cc: [email protected]
Subject: Re: Starting build-system work (Windows/Mac users please speak up)
Date: Fri, 29 May 2020 09:21:49 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<CAASLQ4OdOma6h5Mu=hMEPyk0M4-MomYZLnhGH+2wVoL1vt_UEg@mail.gmail.com>
	<[email protected]>
	<CAASLQ4P11FFgefy_xK0Tcw3vWt1F1MNyVgK5eU=PFGvYrpZcyw@mail.gmail.com>
	<[email protected]>

On 05/29/20 08:14, Chapman Flack wrote:
> It may take some study and iteration to figure out patterns to search for
> in that output that will be sensitive to the most useful messages. But
> just getting the output saved somewhere is a good start.

Honestly, looks like the vast majority are local refs exceeding capacity in
com.sun.management.internal.DiagnosticCommandImpl.getDiagnosticCommandInfo.

I think a whole sequence like this is one warning and its stack trace:

INFO:  WARNING: JNI local refs: %d, exceeds capacity: %d
INFO:  	at com.sun.management.internal.DiagnosticCommandImpl.getDiag...
INFO:  	at ...
...(22 more lines)...
INFO:  	at java.lang.management.ManagementFactory.getPlatformMBeanServer...
INFO:  	- locked <%#016x>
INFO:  (a java.lang.Class for java.lang.management.ManagementFactory)
INFO:  	at org.postgresql.pljava.internal.DualState.<clinit>...


I was scratching my head why DualState.<clinit> would be getting called
so many times (I was expecting *one*), but I think what happens is it
starts the PlatformMBeanServer off in its own thread and that just reuses
the whole stack trace it inherited at birth forever.

I am pretty sure if sequences of just that one pattern were filtered out,
the result would be way, way shorter and the messages remaining in it
would be interesting ones.

Regards,
-Chap

view thread (47+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Starting build-system work (Windows/Mac users please speak up)
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox