Buttons disabled

Issue Type: Bug

Write a small Hello World java app with several lines. Set a breakpoint on first line. Start debugging. After the first break point is hit, press step over button in Debug Toolbar. At this point the Step Over, Step Into, Step Out Of buttons are all incorrectly disabled and the Play button changed to a Pause. You can press the Pause to re-enable other buttons.

This behavior continues through out the debug session.

The expected behavior after the first Step Over operation is that the other Step buttons remain enabled and DON'T require the press of Pause to continue debugging.

Extension version: 0.12.2
VS Code version: Code 1.27.0 (7b9afc4196bda60b0facdf62cfc02815509b23d6, 2018-09-05T05:22:06.672Z)
OS version: Darwin x64 17.7.0

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8 x 2600)
GPU Status	2d_canvas: enabled checker_imaging: disabled_off flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: enabled rasterization: enabled video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled
Load (avg)	2, 2, 2
Memory (System)	16.00GB (0.74GB free)
Process Argv	/Applications/Visual Studio Code.app/Contents/MacOS/Electron -psn_0_5248257
Screen Reader	no
VM	0%

i just tried in latest VSCode, the debug toolbar is correctly displayed. Anyway my platform is win 10. Let me try Mac later.

Let me try a new simple HelloWorld app and make sure I can reproduce it.

…

On Thu, Sep 6, 2018 at 7:54 AM Jinbo Wang ***@***.***> wrote: i just tried in latest VSCode, the debug toolbar is correctly displayed. Anyway my platform is win 10. Let me try Mac later. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#411 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAI6rWfMszc7xETplR3KfGNVLfeGn55Iks5uYQ0FgaJpZM4WctBZ> .

Tried the same HelloWorld project on my Windows 10 and my Macbook. Window 10 version works as expected, MacOS version shows the same problematic behavior described in my bug report. Must be a MacOS thing.

…

On Thu, Sep 6, 2018 at 7:54 AM Jinbo Wang ***@***.***> wrote: i just tried in latest VSCode, the debug toolbar is correctly displayed. Anyway my platform is win 10. Let me try Mac later. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#411 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAI6rWfMszc7xETplR3KfGNVLfeGn55Iks5uYQ0FgaJpZM4WctBZ> .

the same is on kubuntu 18.4
It appeared after vscode update
current VSCode version 1.27.1
plugin version 0.12.2

Dmitry Dutikov (@dancecoder)

Dmitry Dutikov (@dancecoder) Could you please provide the errors in problem view?

Unfortunately Developer console has no errors.
My steps for reproduce:

create a simple project with pom.xml
create a class and test class with a test method (I use JUnit).
build the project with maven
togle a break point in the test class or the project class
Click the debug test gray label above the test method
click Step Over on debug-actions-widget (once or few times)
got: debugging looks paused (the Step Over button is disabled)
expected: not paused and ready for Step Over
make rounded eyes and click Pause on debug-actions-widget
got: unpaused and ready for Step Over
Repeat from point 6 until you eyes is not squere

environment:
kubuntu 18.4
VSCode 1.27.1
vscode-java-debugger 0.12.2
vscode-java-test 0.8.0
vscode-maven 0.10.0
redhat.java 0.30.0
editorconfig 0.12.4
all settings (except editorconfig) is default

As I wrote I got this behavior after vscode update to latest version. Let me know if I able to change some option to provide some additional information.

I've changed java.debug.logLevel to info and got the next error in DeveloperConsole

  ERR Cannot read property 'lineNumber' of null: TypeError: Cannot read property 'lineNumber' of null
	at Object.e.to (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:692:25)
	at e.provideHover (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:749:117)
	at /usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:763:824
	at e._withAdapter (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:761:91)
	at e.$provideHover (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:763:786)
	at e._doInvokeHandler (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:681:309)
	at e._invokeHandler (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:681:27)
	at e._receiveRequest (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:679:802)
	at e._receiveOneMessage (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:678:993)
	at /usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:677:791
	at /usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:98:597
	at e.fire (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:99:917)
	at a (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:164:787)
	at Socket._socketDataListener (/usr/share/code/resources/app/out/vs/workbench/node/extensionHostProcess.js:164:1006)
	at emitOne (events.js:116:13)
	at Socket.emit (events.js:211:7)
	at addChunk (_stream_readable.js:263:12)
	at readableAddChunk (_stream_readable.js:250:11)
	at Socket.Readable.push (_stream_readable.js:208:10)
	at Pipe.onread (net.js:594:20)

not sure is it related to this current problem. After i have changed line feeds to crlf (it was lf) this message is gone

This looks like a vscode regression bug, opened an issue there. microsoft/vscode#58327

I can confirm the same issue on mac.

Windows 10 insider fast ring 17744. I can confirm this error, but on node.js debug step over / step into works as intended. The problem seems to only occur in Java debug i will test other languages to see if the same error happens.

Edit: Debuggers that work as expected
Python
node.js
C/C++

It seems that the problem is only on the java debugger. At least on windows, the vscode update changed internally something about the debugger.

I'm seeing the same issue on Windows 10, with both Java 8 and 10, and VSC 1.27.2 and 1.28.0-insider. Debugger for Java 0.12.2, Java lang support 0.30.0.

Edit: Can confirm that the issue goes away when I revert to VSC 1.26, as per @Fubuchi above.

I get the same error on Ubuntu 18. vscode 1.26 is working fine, you should get back to this version until this bugg get fixed.

was able to duplicate on my machine:
windows 10.
vscode 1.27
debugger 0.12.0

problem went away when i reverted to vscode 1.26.1 as suggested.

I just hit this annoying issue.
Ubuntu 18.04
VSCode 1.27.2
Debugger 0.12.2

Start a debuggin session, buttons get disabled after 1st breakpoint, the only way to continue is pausing the debuggin session and restarting to the next breakpoint

Through the discussion with VS Code team, the StoppedEvent should be sent after StepResponse and ContinueResponse. So we submit a fix to fix the StoppedEvent order. This fix works well for single thread scenario. But for multiple threads scenario, the debug buttons disabled issue is still probably existing. We're communicating back to VS Code team about the new scenario.

The new release 0.13.0 with the fix is just released, in case you want to have a try. And please let us know if you found new issues. Thanks.

Just tried it with simple Hello World java debug and with Spring Boot java remote debug. Both work fine. Debug toolbar buttons stay enabled throughout the session. Thanks

…

On Wed, Sep 19, 2018 at 6:39 AM Jinbo Wang ***@***.***> wrote: Through the discussion with VS Code team, the StoppedEvent should be sent after StepResponse or ContinueResponse. So we submit a fix to fix the StoppedEvent order. This fix works well for single thread scenario. But for multiple threads scenario, the debug buttons disabled issue is still probably existing. We're communicating back to VS Code team about the new scenario. The new release 0.13.0 with the fix is just released, in case you want to have a try. And please let us know if you found new issues. Thanks. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#411 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAI6rUWda7A-i4N7j-6mmYUe37HkQbbyks5uch7ogaJpZM4WctBZ> .

Bill Pfeiffer (@wpfeiffe)

Bill Pfeiffer (@wpfeiffe) Thanks for the verification.

VS Code team has pushed a fix for the multiple threads scenario, it's in the 2018-09-20 insider. And i verified it works. Close this issue first. If you guys find the issue is still not resolved, welcome to reopen it.

Navigation Menu

Repository navigation

Buttons disabled #411

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Buttons disabled #411

Description

Activity

testforstephen commented on Sep 6, 2018

wpfeiffe commented on Sep 6, 2018

wpfeiffe commented on Sep 6, 2018

dancecoder commented on Sep 8, 2018

andxu commented on Sep 8, 2018

dancecoder commented on Sep 8, 2018

dancecoder commented on Sep 8, 2018

testforstephen commented on Sep 10, 2018

aleeraser commented on Sep 11, 2018

Windblade-GR01 commented on Sep 13, 2018

Sindisil commented on Sep 13, 2018

alex-cornejo commented on Sep 13, 2018

joshryanne commented on Sep 13, 2018

adrianmoya commented on Sep 14, 2018

testforstephen commented on Sep 19, 2018

wpfeiffe commented on Sep 19, 2018

testforstephen commented on Sep 20, 2018

testforstephen commented on Sep 25, 2018

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions