[Frontend] useStreamEvents tears down and recreates the EventSource on every render - SSE reconnect storm/leak

[grantfox-oss]

Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0

Why this matters

frontend/src/hooks/useStreamEvents.ts:47-64 - buildUrl's useCallback depends on streamIds, whose default streamIds = [] is a fresh array each render, and every call site passes an inline array. New identity -> buildUrl -> connect change -> the mount effect with deps [connect] closes and reopens the EventSource on every render. Each received event calls setEvents, re-rendering the consumer, so the stream reconnects on every event - a self-sustaining reconnect loop and resource leak.

Acceptance criteria

• Memoize subscription identity (derive a stable string key from streamIds/subscribeToAll/jwtToken) so connect/buildUrl only change when the subscription changes
• EventSource is created once per distinct subscription, not per render or per received event
• Clear any pending reconnect timer before scheduling a new one and cap reconnect attempts
• Add a regression test asserting only one EventSource instance is created across multiple re-renders and incoming events

Files to touch

• frontend/src/hooks/useStreamEvents.ts
• frontend/src/components/NotificationDropdown.tsx
• frontend/src/components/dashboard/dashboard-view.tsx
• frontend/src/app/streams/[id]/page.tsx

Out of scope

• Backend SSE controller changes

[dextro172-ui]

@dextro172-ui has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would love to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @dextro172-ui to this issue.

[heymide]

@heymide has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I've reviewed the task and have a clear implementation plan. Looking forward to contributing with a quality PR.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @heymide to this issue.

[Akpolo]

@Akpolo has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

hi maintainer,please i'll love to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Akpolo to this issue.

[Delightech28]

@Delightech28 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I'd like to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Delightech28 to this issue.

[Rampop01]

@Rampop01 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would like to work on this issue . I understand the assignment and the requirements, and I’m confident in the approach needed to deliver the best solution. Kindly assign this task to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Rampop01 to this issue.

[Caneryy]

@Caneryy has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello, please can I work on this issue?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Caneryy to this issue.

[grantfox-oss]

🦊 GrantFox — @Rampop01 has been assigned to this issue!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #850)
2. Your PR will be reviewed by the LabsCrypt maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

Congratulations, @Rampop01! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @Rampop01: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊