Skip to content

Debug adapter process has terminated unexpectedly #63

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

Closed
sswaroopgupta opened this issue Apr 26, 2018 · 9 comments
Closed

Debug adapter process has terminated unexpectedly #63

sswaroopgupta opened this issue Apr 26, 2018 · 9 comments
Assignees

Comments

@sswaroopgupta
Copy link
Contributor

Expected behavior
Should be able to debug seamlessly

Actual behavior
Debug adapter process has terminated unexpectedly

Steps to replicate

  • Create a gauge-python project
  • Debug Spec
  • Debug Scenario
  • Debug Spec

The message appears Debug adapter process has terminated unexpectedly

Version

Gauge version: 0.9.8.nightly-2018-04-26
Commit Hash: 5bd699e

Plugins
-------
python (0.3.0.nightly-2018-04-26)
@sswaroopgupta
Copy link
Contributor Author

The Python process CPU usage is almost 100 in this scenario when Debugging is hung

@BugDiver
Copy link
Member

BugDiver commented Apr 30, 2018

Cause of the Issue

Possible fix/workaround

  • Vscode does not provide a way the handle debug the crash,
  • A timeout can be added in runners after which runner can print on the console that debugger did not attach in given time and quit.
  • vscode can intercept the console output and Show notification and stop the running gauge process.

@BugDiver
Copy link
Member

the fix should be available in following nightlies -

  • gauge-vscode - 30-04-2018
  • gauge-python - 30-04-2018

@sswaroopgupta
Copy link
Contributor Author

Verified on OSx. Still replicable on with version

Gauge version: 0.9.8.nightly-2018-05-01
Commit Hash: 765d3e7

Plugins
-------
csharp (0.10.3.nightly-2018-04-11)
html-report (4.0.4.nightly-2018-04-11)
java (0.6.7.nightly-2018-04-24)
js (2.2.0.nightly-2018-04-20)
python (0.3.0.nightly-2018-05-01)

VSCode Version - gauge-0.0.4.nightly-2018-05-01.vsix

@BugDiver
Copy link
Member

BugDiver commented May 2, 2018

@sguptatw Can you tell what are you getting?

@sswaroopgupta
Copy link
Contributor Author

sswaroopgupta commented May 2, 2018

Debug adapter process has terminated unexpectedly
The steps to replicate are the same as the original issue.

Observation: The number of times the Debug Spec and Debug Scenario can vary.

@BugDiver
Copy link
Member

BugDiver commented May 2, 2018

@sguptatw We can't fix debugger crash problem coz it's a problem with vscode-python.
The fix is about the high CPU usage. Please refer the above comment. It's a workaround which we have done.

@sswaroopgupta
Copy link
Contributor Author

@BugDiver The user should be able to stop debugging and proceed with other IDE actions.
Clicking on stop debugging does not stop the gauge process/debugging process. Currently user has to restart the IDE to continue with other IDE actions.

@sswaroopgupta
Copy link
Contributor Author

This issue has been de-prioritized right now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants