Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Unable to parse these lines with GC promotion and reference GC information #76

Closed
haridsv opened this issue Sep 6, 2013 · 4 comments
Closed
Assignees
Milestone

Comments

@haridsv
Copy link

haridsv commented Sep 6, 2013

When I opened a logfile, I got the below warnings:

WARNING [DataReaderSun1_6_0]: com.tagtraum.perf.gcviewer.imp.ParseException: Error parsing entry (java.lang.NumberFormatException: For input string: "4172533K->4251241K(4323712K).") Line 1357: 2013-09-02T18:22:23.195+0000: 1837.498: [GC1837.600: [SoftReference, 0 refs, 0.0000060 secs]1837.600: [WeakReference, 374 refs, 0.0000550 secs]1837.600: [FinalReference, 347 refs, 0.0002090 secs]1837.600: [PhantomReference, 0 refs, 0.0000020 secs]1837.600: [JNI Weak Reference, 0.0000050 secs]-- [PSYoungGen: 1330796K->1330796K(1403264K)] 4172533K->4251241K(4323712K), 0.6580190 secs] [Times: user=2.35 sys=0.02, real=0.66 secs] 
WARNING [DataReaderSun1_6_0]: com.tagtraum.perf.gcviewer.imp.ParseException: Error parsing entry (java.lang.NumberFormatException: For input string: "4666565K->4772019K(4772032K).") Line 2986: 2013-09-02T18:57:22.049+0000: 3936.352: [GC3936.408: [SoftReference, 0 refs, 0.0000050 secs]3936.408: [WeakReference, 245 refs, 0.0000450 secs]3936.408: [FinalReference, 475 refs, 0.0003260 secs]3936.408: [PhantomReference, 0 refs, 0.0000030 secs]3936.409: [JNI Weak Reference, 0.0000040 secs]-- [PSYoungGen: 1851577K->1851577K(1851584K)] 4666565K->4772019K(4772032K), 0.6971770 secs] [Times: user=1.63 sys=0.00, real=0.70 secs] 
WARNING [DataReaderSun1_6_0]: com.tagtraum.perf.gcviewer.imp.ParseException: Error parsing entry (java.lang.NumberFormatException: For input string: "4654087K->4800467K(4800512K).") Line 3330: 2013-09-02T19:06:10.952+0000: 4465.255: [GC4465.311: [SoftReference, 0 refs, 0.0000050 secs]4465.311: [WeakReference, 409 refs, 0.0000710 secs]4465.311: [FinalReference, 612 refs, 0.0004330 secs]4465.311: [PhantomReference, 0 refs, 0.0000020 secs]4465.311: [JNI Weak Reference, 0.0000040 secs]-- [PSYoungGen: 1880026K->1880026K(1880064K)] 4654087K->4800467K(4800512K), 0.7018690 secs] [Times: user=1.62 sys=0.00, real=0.70 secs] 

It appears like the issue is with the promotion failure marker "--" appearing in them. When I edited out those markers from these lines, it was happy.

@ghost ghost assigned chewiebug Sep 8, 2013
chewiebug added a commit that referenced this issue Sep 8, 2013
@chewiebug
Copy link
Owner

Hmm, not very nice of the logger to separate the type name and the promotion failure ;-).

I have still found a fix to this issue.

Regards, Jörg

@haridsv
Copy link
Author

haridsv commented Sep 11, 2013

Thank you, will give it a try.

@haridsv
Copy link
Author

haridsv commented Sep 12, 2013

I noticed that the GC-Type is extracted as "GC--", is this intentional? It would be better to show it as "GC" and capture a separate stat for number of promotion failures.

@chewiebug
Copy link
Owner

Hi Hari,

I just realised that I forgot to answer here - I am sorry!

It is intentional, that the type extracted is "GC--", because the
promotion failure is part of that GC. You get separate stats for events
with and without promotion failures ("GC--" are those with promotion
failure, all others not).

Regards, Jörg

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants