Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Translate JFR stacktrace symbols #109

Merged
merged 9 commits into from
Jul 1, 2024
Merged

Conversation

dagguh
Copy link
Contributor

@dagguh dagguh commented Jun 28, 2024

Result so far:
image

@dagguh dagguh force-pushed the translate-jfr-stacktrace-symbols branch from ec12c6f to 749605f Compare July 1, 2024 13:39
@dagguh dagguh marked this pull request as ready for review July 1, 2024 13:39
@dagguh dagguh requested a review from a team as a code owner July 1, 2024 13:39
@mgrzaslewicz
Copy link
Contributor

mgrzaslewicz commented Jul 1, 2024

Before - split in flamegraph when compared 2 files having in fact the same stack traces

image

After - no split in flamegraph

image

mgrzaslewicz
mgrzaslewicz previously approved these changes Jul 1, 2024
@dagguh dagguh force-pushed the translate-jfr-stacktrace-symbols branch from ca9d5ce to 26d975f Compare July 1, 2024 14:05
mgrzaslewicz
mgrzaslewicz previously approved these changes Jul 1, 2024
dagguh added 4 commits July 1, 2024 16:10
Naming the byte array as an explicit type gives us:
- one Javadoc to explain the contents
- memoized `new String(bytes)`

Also clean up dead code and add missing changelog.
The forced loop-reading was inherited from JMC, but we don't know its purpose.
The simpler one-shot impl passes our tests and the output JFR opens in IntelliJ.

PS. remove unncessary ByteArray clone.
@dagguh dagguh force-pushed the translate-jfr-stacktrace-symbols branch from 26d975f to e36389d Compare July 1, 2024 14:11
@dagguh dagguh merged commit a391e19 into master Jul 1, 2024
3 checks passed
@dagguh dagguh deleted the translate-jfr-stacktrace-symbols branch July 1, 2024 14:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants