Skip to content

Android debugging is leaking the debug session #4219

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
DimitarTachev opened this issue Dec 11, 2018 · 1 comment
Closed

Android debugging is leaking the debug session #4219

DimitarTachev opened this issue Dec 11, 2018 · 1 comment

Comments

@DimitarTachev
Copy link
Contributor

Environment
Provide version numbers for the following components (information can be retrieved by running tns info in your project folder or by inspecting the package.json of the project):

  • CLI: 5.1.0
  • Cross-platform modules: 5.0.0
  • Android Runtime: 5.0.0
  • iOS Runtime: 5.0.0

To Reproduce

  1. tns create testApp --js && cd testApp
  2. tns debug android
  3. Open the Chrome URL and set a breakpoint.
  4. Run ctrl + c in order to terminate the debug command.
  5. Try to hit your breakpoint.
  6. The breakpoint will be successfully hit.

Expected behavior
The debug session should be terminated along with the CLI debug command.

@rosen-vladimirov
Copy link
Contributor

Once the session is established and CLI command exits, CLI will remove the port forwarding. But the connection between Chrome DevTools and device is already setup, so it will continue to live. If you refresh DevTools or restart app on device, the connection will not be established anymore.
So I'm closing this issue as CLI no longer leaks forwarded ports.

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

No branches or pull requests

2 participants