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

"Open Loaded Scripts" often doesn't work on second run #22418

Closed
roblourens opened this issue Mar 10, 2017 · 3 comments
Closed

"Open Loaded Scripts" often doesn't work on second run #22418

roblourens opened this issue Mar 10, 2017 · 3 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues *duplicate Issue identified as a duplicate of another issue(s)
Milestone

Comments

@roblourens
Copy link
Member

roblourens commented Mar 10, 2017

Not every time, but

  • Start legacy protocol debug session
  • Open something via "Open loaded scripts"
  • Stop debugging
  • Start debug session again
  • Open same script as before

Nothing happens. Debugging, I see that at

vscode.workspace.openTextDocument(uri).then(doc => {
  vscode.window.showTextDocument(doc);
});

openTextDocument returns undefined, and showTextDocument fails.

@weinand weinand added bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues labels Mar 10, 2017
@roblourens
Copy link
Member Author

roblourens commented Mar 10, 2017

I just noticed that I see something similar for eval scripts in general - have eval('debugger'). It will load the source during the first debug session, but not in subsequent debug sessions, unless the window is reloaded. Maybe related.

@isidorn
Copy link
Contributor

isidorn commented Mar 17, 2017

FYI might be connected to #22741

@weinand weinand added this to the April 2017 milestone Apr 5, 2017
@weinand
Copy link
Contributor

weinand commented Apr 21, 2017

yes, dup of #22741

@weinand weinand closed this as completed Apr 21, 2017
@weinand weinand added the *duplicate Issue identified as a duplicate of another issue(s) label Apr 21, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues *duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

3 participants