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

Debugging control bar disappears #83771

Closed
doogie99 opened this issue Oct 31, 2019 · 12 comments
Closed

Debugging control bar disappears #83771

doogie99 opened this issue Oct 31, 2019 · 12 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues verified Verification succeeded
Milestone

Comments

@doogie99
Copy link

Issue Type: Bug

I don't know how to recreate this but this seems to have been introduced in the last month or so.

I often debug Golang code in VS Code. When I start debugging I get the debugging control bar showing up near top of screen. For some reason it occasionally disappears now while the debugger is still running. If you try to start a new debugging session you get an error that says something to the effect of "debugging session already running".

Could this be a z-order problem?

VS Code version: Code 1.39.2 (6ab5985, 2019-10-15T15:35:18.241Z)
OS version: Windows_NT x64 10.0.18362

Extensions (11)
Extension Author (truncated) Version
numbered-bookmarks ale 6.2.1
ng-template Ang 0.802.3
atlascode atl 2.1.4
gitlens eam 10.1.1
EditorConfig Edi 0.14.2
prettier-vscode esb 2.3.0
contextualduplicate laf 0.2.0
Go ms- 0.11.7
vscode-typescript-tslint-plugin ms- 1.2.2
debugger-for-chrome msj 4.12.1
vscode-yaml red 0.5.3
@vscodebot
Copy link

vscodebot bot commented Oct 31, 2019

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

@isidorn
Copy link
Contributor

isidorn commented Nov 13, 2019

Very simmilar to an issue @joaomoreno is hitting
I plan to look into this

@isidorn isidorn added the debug Debug viewlet, configurations, breakpoints, adapter issues label Nov 13, 2019
@isidorn isidorn added this to the November 2019 milestone Nov 13, 2019
@isidorn
Copy link
Contributor

isidorn commented Nov 27, 2019

@doogie99 do you maybe have better steps to reproduce this? I would really appreciate it.
What I suspect is happening is that the debugee shuts down, the toolbar as tha cause of that disappears. And some state is left behind.
When this happens is the debug status bar still orange?

@isidorn isidorn modified the milestones: November 2019, December 2019 Nov 27, 2019
@isidorn isidorn added the info-needed Issue requires more information from poster label Nov 27, 2019
@doogie99
Copy link
Author

@isidorn I haven't had it happen for a bit but next time I see it I'll try to be attentive to the debug status bar. I usually use this when debugging golang code that provides the api for our app. When the debug controls disappear the api is still running and responsive. I suspected that the missing controls was just a zorder thing but I could not reveal the controls no matter what I tried.

@isidorn
Copy link
Contributor

isidorn commented Nov 27, 2019

Nope, I do not think the issue is css.
Let me know if you find more details next time it happens. Would really appreciate it. Thanks

@vscodebot vscodebot bot closed this as completed Dec 4, 2019
@vscodebot
Copy link

vscodebot bot commented Dec 4, 2019

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

@doogie99
Copy link
Author

doogie99 commented Dec 6, 2019

@isidorn

So, here's some more info. I'm currently in the problematic state where the debugger is not running but my golang api code is still running and there is no obvious way to shut it down in the debugger.

If I try to start a debug session with my current debug configuration it says:

"There is already a debug configuration [My golang debug config] running"

The Debug menu looks like this:

image

I found the Debug toolbar in the HTML and forced it to display (it was display: none) but even after doing so the controls on it are ineffective. This didn't surprise me with the Debug menu having the same controls disabled.

I have Dev Tools open. Here's the contents of the JS Console:

JS console debug fail.txt

Hope that helps.

-D

@isidorn
Copy link
Contributor

isidorn commented Dec 9, 2019

Thanks a lot, let's reopen and assign for December so I investigate more

@isidorn isidorn added under-discussion Issue is under discussion for relevance, priority, approach and removed info-needed Issue requires more information from poster labels Dec 9, 2019
@isidorn isidorn reopened this Dec 9, 2019
@isidorn
Copy link
Contributor

isidorn commented Dec 12, 2019

There will be a new visual studio release in a couple of days.
Can you pease let us know if you can still repro the issue with that latest release 1.41

@isidorn isidorn added info-needed Issue requires more information from poster and removed under-discussion Issue is under discussion for relevance, priority, approach labels Dec 12, 2019
@isidorn isidorn removed this from the December/January 2020 milestone Dec 12, 2019
@vscodebot vscodebot bot closed this as completed Dec 19, 2019
@vscodebot
Copy link

vscodebot bot commented Dec 19, 2019

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

@isidorn
Copy link
Contributor

isidorn commented Jan 22, 2020

@joaomoreno here's the issue you are seeing. Reopening and assigning to this milestone to investigate more and potentially handle this better.

@isidorn isidorn reopened this Jan 22, 2020
@isidorn isidorn added bug Issue identified by VS Code Team member as probable bug and removed info-needed Issue requires more information from poster labels Jan 22, 2020
@isidorn isidorn added this to the January 2020 milestone Jan 22, 2020
@isidorn
Copy link
Contributor

isidorn commented Jan 29, 2020

I could reproduce this partially if I start a comound configuration and one of the configuration has issues starting. Then the focused session was not begin properly set and the debug toolbar would be invisible.
I have pushed a fix for this issue.
@joaomoreno please let me know if you still see this starting from tomorrow. Thanks!

@eamodio eamodio added the verified Verification succeeded label Jan 31, 2020
@vscodebot vscodebot bot locked and limited conversation to collaborators Mar 14, 2020
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 verified Verification succeeded
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants