BUG:Resource Leak in WebSocket Handler - Asyncio Task Not Properly Awaited After Cancellation

[yugalkaushik]

Is there an existing issue for this?

• I have searched the existing issues

What happened?

📌 Issue Overview

The WebSocket endpoint in Backend/app/routes/chat.py has a resource leak vulnerability where asyncio tasks are cancelled but not properly awaited, preventing cleanup code from executing and potentially leaving Redis pubsub connections open.

In the WebSocket handler's exception blocks, when a WebSocketDisconnect or general Exception occurs, the code cancels the listener_task but does not await it:

except WebSocketDisconnect:
    listener_task.cancel()
    await chat_service.disconnect(user_id, redis, db)

except Exception as e:
    listener_task.cancel() 
    await chat_service.disconnect(user_id, redis, db)

Record

• I agree to follow this project's Code of Conduct
• I want to work on this issue

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!