-
Notifications
You must be signed in to change notification settings - Fork 319
Automatically register crashtracking via native extensions #8851
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
Merged
jbachorik
merged 16 commits into
master
from
mattalp/reroute-gradle-profiler-dependencies
Jul 16, 2025
Merged
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
b1d60ff
Add ddprof-lib library wrapper module
jbachorik 233e0ce
Move TempLocationManager to internal-api
jbachorik 0c372fb
Rework crash-tracking to allow auto-injection of JVM arguments for er…
jbachorik cf60ece
Fix smoke test confused by extra logging
jbachorik 6f28638
Restrict method visibility
jbachorik f36590f
Spotless
jbachorik d061ea0
Fix merge breakage
jbachorik 239552e
Avoid ConfigProvider early in the agent startup
jbachorik 8b45e6c
Allow soft-rollout with crashtracking auto-config only if ddprof-java…
jbachorik f37c464
Merge branch 'master' into mattalp/reroute-gradle-profiler-dependencies
jbachorik 0069b78
Fix post-merge issue
jbachorik 6603c07
Merge branch 'master' into mattalp/reroute-gradle-profiler-dependencies
jbachorik 6aea22d
Spotbugs
jbachorik 380fa3c
Merge branch 'mattalp/reroute-gradle-profiler-dependencies' of github…
jbachorik 920ab21
Add comment
jbachorik c05d545
Measure crashtracking initialization
jbachorik File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmmm, is the logic reversed? and why delay value not used?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The change here is only about adding the
finallyblock to clean up thePROFILER_INIT_AFTER_JMXvariable.I agree that the code is a bit confusing - basically, when
getJmxStartDelay()is set to 0 we will attempt to initialize the JMX subsystem as soon as available. But - this can cause issues with JFR as it needs some 'grace period' after JMX is ready. That's why we are re-scheduling the profiler initialization code just a tad later.If the jmx start delay is set, we are already delayed relative to the jmx init so we can just plainly run the initialization code.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nitpick: Might be worth putting this comment as comment in the code ;)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jbachorik I meant that your comment is well written and could land as a comment in the code.