Guard against null heap profile #252
Merged
+3
−0
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.
What does this PR do?:
Adds a check for whether the profile returned from
v8::HeapProfiler::GetAllocationProfile()is null and throws an exception when it is.Motivation:
We observed a crash in the wild at this location. It's possible we have a race condition between the cleanup hook and this method. Since the method is normally invoked once every ~60 seconds, the condition occurs very rarely. It's still better to throw an exception in JS (same as here before invoking the now modified method) than crash the process. dd-trace-js catches these exceptions and handles them gracefully.
Jira: PROF-13456