gc logs [Full GC (System)
Y. S. Ramakrishna
y.s.ramakrishna at oracle.com
Thu Feb 10 11:18:25 PST 2011
Of course that also circumvents -XX:+ExplicitGCInvokesConcurrent.
On 02/10/11 11:15, Y. S. Ramakrishna wrote:
> On 02/10/11 10:46, Kirk wrote:
>> sed also works well in getting rid of calls to System.gc()... and it
>> guarantees that it won't accidentally show up again.
>> On Feb 10, 2011, at 7:25 PM, Peter Schuller wrote:
>>>> please help me understand in following 2 line if
>>>> Full GC (System)
>>>> means this is caused due to System.gc() call ?
>>> If you're having trouble with code calling System.gc(),
>>> -XX:+DisableExplicitGC may be an option. But that will also disable
>>> e.g. jconsole triggered GC:s (I think).
> a hack ;-) to cause an explicit gc even when it's disabled
> via the above flag is to use jmap -histo:live on the JVM.
> -- ramki
hotspot-gc-use mailing list
hotspot-gc-use at openjdk.java.net
More information about the hotspot-gc-dev