microsoft / microsoft/gctoolkit
Unified logs missing time stamps causes NPE
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.3k
- Forks
- 177
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 3
Description
Unified GC logs without a timestamp will cause NPE as all of the code expects a timestamp. Use first date stamp as a base of 0.000 seconds and then synthetically generate timestamps for each JVMEvent.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing unified GC log parsing and the JVMEvent timestamp handling, then reproduce the NPE with a log that lacks timestamps. The issue is done when such logs no longer fail and each JVMEvent receives a synthetic timestamp based on the first date stamp at 0.000 seconds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- performance, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100