-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
feat(anr): Improve ANR root cause analysis #49673
Conversation
static/app/components/events/interfaces/frame/deprecatedLine.tsx
Outdated
Show resolved
Hide resolved
|
||
for (let index = 0; index < exceptionFrames.length; index++) { | ||
// iterating the frames in reverse order, because the topmost frames most like the root cause | ||
for (let index = exceptionFrames.length - 1; index > 0; index--) { |
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.
What's the max number of frames here? If it's really low we don't really need an early exit by reverse walking this array. Up to you though.
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.
we need the early exit here in case there are multiple offending frames. The UI is only capable of rendering a single root cause and we're picking the one that is the closest to the exception root cause, that's why we reverse it. Unless I misunderstood your comment :)
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.
Ah there are multiple, nevermind 👍
@k-fish I've merged this, lemme know if I misunderstood and should follow up with some changes. Thank you |
The PR includes 3 main changes:
Tag
component. When the Tag is clicked it automatically scrolls to the Suspect Root Cause section.