[Bug]: websocket app demo connection cleanup

[philhosophy]

File Name

gemini/multimodal-live-api/websocket-demo-app/backend/main.py

What happened?

closing connections and cleanup

Relevant log output

websockets.exceptions.ConnectionClosedError: received 1011 (internal error) Request trace id: f102afa6f090070d, [ORIGINAL ERROR] generic::resource_exhausted: RESOURCE_EXHAUSTED: Maximum concurrent se; then sent 1011 (internal error) Request trace id: f102afa6f090070d, [ORIGINAL ERROR] generic::resource_exhausted: RESOURCE_EXHAUSTED: Maximum concurrent se

Code of Conduct

• I agree to follow this project's Code of Conduct

[rajeevrj256]

Your WebSocket server ran out of resources due to too many connections or insufficient system capacity. The error RESOURCE_EXHAUSTED means the maximum allowed concurrent connections were reached, causing the server to close connections with an internal error.

Fix it by:

Increasing server resource limits.
Closing idle or unused WebSocket connections.
Adding load balancing for high traffic.
Debugging connection cleanup in your backend code.

[philhosophy]

Thank you for the reply and the detailed explanation and proposed solutions. I will look into them.

[hupili]

@philhosophy , did you figure out a way to cleanup connection?

[andrewksmith12]

+1, the multimodal live api notebook needs connection cleanups to be added- I've hit resources exhausted multiple times.

[AozakiHayate]

Thanks for the insights!

I also encountered this issue in both the notebook and local demo—refreshing the page multiple times leads to a 1011 (RESOURCE_EXHAUSTED) error, and I have to wait for the API to release resources. I'm still investigating how to properly clean up WebSocket connections. If anyone has suggestions, I'd appreciate the help!