Parser rule missed #192
-
I find gctoolkit can't parse my gc log and show that |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Converted this to an issue, it's a bug :-) |
Beta Was this translation helpful? Give feedback.
-
Hi @ZhangShushu123, Do you have the complete log for this missing line? If so, can you share it? If you would like the pleasure of fixing this bug I'm happy to assign it to you and I'm happy to assist. This rule would be defined in CMSPatterns as a GCParseRule. It would be parsed and interpreted in GenerationalHeapParser. In this case I'd like to see the lines just before this line to confirm how to interrupt this. At the moment I'm seeing this as a Concurrent Mode Failure but as a Full GC caused by an allocation failure, not from a promotion failure. This feels like a large allocation from a mutator thread directly into tenured. You can setup testing for the rule in ConcurrentMarkSweepParserRulesTest. There should be one other test that makes sure the capture groups match what you think they should match and then you may break the tests that are counting events. |
Beta Was this translation helpful? Give feedback.
Hi @ZhangShushu123, Do you have the complete log for this missing line? If so, can you share it? If you would like the pleasure of fixing this bug I'm happy to assign it to you and I'm happy to assist.
This rule would be defined in CMSPatterns as a GCParseRule. It would be parsed and interpreted in GenerationalHeapParser. In this case I'd like to see the lines just before this line to confirm how to interrupt this. At the moment I'm seeing this as a Concurrent Mode Failure but as a Full GC caused by an allocation failure, not from a promotion failure. This feels like a large allocation from a mutator thread directly into tenured.
You can setup testing for the rule in ConcurrentMarkSweepPa…