-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
Call stack items aren't opening tabs with correct contents #136684
Comments
No idea from my end, would be good to have a simple repro. |
One thing I did change recently, not sure whether it could be the reason though: when you call Refs: 6ed67dd |
I couldn't reproduce this. |
I can reproduce this consistently. You just need an item in the callstack that is from a file that's different from the topmost item. |
Repro steps for me
It activates the tab, but the contents are from the jsonOutline.ts file: |
@rchiodo thanks for the steps, now I can reproduce! (without your detailled steps I was trying a web-packed extension which only has one underlying *.js file but maps to many *.ts files). In my case (on macOS) I do not see the wrong contents, but no contents at all: |
/verified. Opened tabs are correct. |
While debugging extensions, if I stop at a break point and try to walk back up the call stack, the tabs that get opened from the call stack view have the correct tab name, but don't initially have the correct contents. But if you switch to a different tab and then back, the proper contents get shown.
This started quite recently (in insiders).
/cc @connor4312 @bpasero
The text was updated successfully, but these errors were encountered: