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

[bug] Port does not close if window closed. #3292

Closed
bicarlsen opened this issue Jan 27, 2022 · 1 comment
Closed

[bug] Port does not close if window closed. #3292

bicarlsen opened this issue Jan 27, 2022 · 1 comment
Labels
status: invalid This is not a valid issue type: bug

Comments

@bicarlsen
Copy link

Describe the bug

It appears that the port does not close if the tauri app is closed form the window close button rather than the command line.

Reproduction

  1. Start tauri in dev mode, e.g. yarn tauri dev
  2. Close the app window with the close button rather than terminating the process in the command line. The command line process terminates as well
  3. Start tauri in dev mode again, it now asks to use a different port because the original one is in use.

Expected behavior

Port should close when process terminates, regardless of how it terminates.

Platform and versions

Operating System - Ubuntu, version 21.04 X64

Node.js environment
  Node.js - 17.1.0
  @tauri-apps/cli - 1.0.0-beta.10
  @tauri-apps/api - 1.0.0-beta.8

Global packages
  npm - 8.1.2
  yarn - 1.22.17

Rust environment
  rustc - 1.56.1
  cargo - 1.56.0

App directory structure
/.vscode
/.git
/node_modules
/src-tauri
/src
/dist
/.angular

App
  tauri.rs - 1.0.0-beta.8
  build-type - bundle
  CSP - default-src blob: data: filesystem: ws: wss: http: https: tauri: 'unsafe-eval' 'unsafe-inline' 'self' img-src: 'self'
  distDir - ../dist/thot-desktop
  devPath - http://localhost:4200
  framework - Angular
  bundler - Webpack

Stack trace

No response

Additional context

No response

@amrbashir
Copy link
Member

duplicate of #2794

@lucasfernog lucasfernog added status: invalid This is not a valid issue and removed status: duplicate labels Jul 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: invalid This is not a valid issue type: bug
Projects
None yet
Development

No branches or pull requests

3 participants