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

Callstack shows stale frames when first frame is updated #28044

Closed
roblourens opened this issue Jun 5, 2017 · 2 comments
Closed

Callstack shows stale frames when first frame is updated #28044

roblourens opened this issue Jun 5, 2017 · 2 comments
Assignees
Labels
*as-designed Described behavior is as designed debug Debug viewlet, configurations, breakpoints, adapter issues

Comments

@roblourens
Copy link
Member

Earlier, the callstack would initially update the first frame when stepping, and only show the first frame. Now, it continues to show the rest of the stack when updating the first frame, which seems wrong.

jun-05-2017 08-16-12

jun-05-2017 08-32-52

@isidorn
Copy link
Contributor

isidorn commented Jun 6, 2017

@roblourens we have decided on this after a dicussion in the standup. The reason for showing the stale stack trace is to prevent flickering (which we had originally when first just showing the top stack frame).
You should only see the stale stack trace for half a second and it should update automatically to something meaningfull.

Closing as designed, but will reopen if you have a better suggestion what to do here.

p.s. Another thing we tried is showing the stale stack trace in itallic but then the view would again flicker

@isidorn isidorn closed this as completed Jun 6, 2017
@isidorn isidorn added *as-designed Described behavior is as designed debug Debug viewlet, configurations, breakpoints, adapter issues labels Jun 6, 2017
@roblourens
Copy link
Member Author

Sure, that's fine. I wonder whether we could do something different based on whether the user is stepping quickly many times in a row, or stepping slowly? Will keep thinking about it...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*as-designed Described behavior is as designed debug Debug viewlet, configurations, breakpoints, adapter issues
Projects
None yet
Development

No branches or pull requests

2 participants