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

Actix Ws does not seem to shutdown worker when websocket route finishes #488

Open
soundprojects opened this issue Dec 18, 2024 · 0 comments

Comments

@soundprojects
Copy link

Expected Behavior

When a websocket route that contains some spawned tasks all finish, I expect the worker associated to shut down.

Current Behavior

My websocket route finishes, the spawned tasks finish but only when I shutdown the application do I see a "force shutdown worker, closing x connections" for all the connections that have finished way earlier

Possible Solution

Some pointers on how to diagnose this further

Steps to Reproduce (for bugs)

  1. Use the default websocket example
  2. Spawn some tasks inside the route
  3. Close client
  4. Close server -> see how many connections are closed

Context

Your Environment

  • Rust version (output of rustc -V): 1.8.2
  • actix-* crate versions: actix-ws 0.3.0, actix-web 4.9.0, actix-cors 0.7.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant