github-starred/komodo
2
0
Fork 1
mirror of https://github.com/moghtech/komodo.git synced 2026-05-06 08:55:40 -05:00
Code Issues 3.5k Packages Projects Releases 103 Wiki Activity

[GH-ISSUE #368] Leaving Komodo Web UI in the background makes it send tons of WebSocket connections and drains server's CPU #2136

New Issue
Closed
opened 2026-04-11 10:02:27 -05:00 by GiteaMirror · 13 comments
GiteaMirror commented 2026-04-11 10:02:27 -05:00
Owner
Copy Link

Originally created by @AnotiaWang on GitHub (Mar 18, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/368

Komodo version: v1.17.0
Browser: Vivaldi 7.2.3621.63 (Stable channel) (arm64)

To reproduce:

  1. Open Komodo Web UI in the browser and log in
  2. Leave it in the background (switch to another browser tab or window)
  3. After some time (e.g. half an hour), switch back to Komodo

Behavior:

  • You may notice that the browser become a little unresponsive
  • The indicator on top right corner keeps flashing between red and green
  • If you open the console, you will see hundreds of thousands of errors due to Komodo trying to reconnect to the server
Image
Originally created by @AnotiaWang on GitHub (Mar 18, 2025). Original GitHub issue: https://github.com/moghtech/komodo/issues/368 Komodo version: v1.17.0 Browser: Vivaldi 7.2.3621.63 (Stable channel) (arm64) To reproduce: 1. Open Komodo Web UI in the browser and log in 2. Leave it in the background (switch to another browser tab or window) 3. After some time (e.g. half an hour), switch back to Komodo Behavior: - You may notice that the browser become a little unresponsive - The indicator on top right corner keeps flashing between red and green - If you open the console, you will see hundreds of thousands of errors due to Komodo trying to reconnect to the server <img width="642" alt="Image" src="https://github.com/user-attachments/assets/24d1ac0d-6c3e-4b50-b08f-831b51c810a6" />
GiteaMirror commented 2026-04-11 10:02:28 -05:00
Author
Owner
Copy Link

@Buco7854 commented on GitHub (Mar 28, 2025):

Same thing, getting myself blacklisted from my own server since it triggers ratelimits.

<!-- gh-comment-id:2761203369 --> @Buco7854 commented on GitHub (Mar 28, 2025): Same thing, getting myself blacklisted from my own server since it triggers ratelimits.
GiteaMirror commented 2026-04-11 10:02:29 -05:00
Author
Owner
Copy Link

@Kickbut101 commented on GitHub (Mar 28, 2025):

Same, finding other issues in network (pihole) complaining about lots of requests.

This is my ALL-TIME permitted domains, for my entire network.

Komodo is already # 4 in pihole, and I only installed it last week...

Image

<!-- gh-comment-id:2762327321 --> @Kickbut101 commented on GitHub (Mar 28, 2025): Same, finding other issues in network (pihole) complaining about lots of requests. This is my ALL-TIME permitted domains, for my entire network. Komodo is already # 4 in pihole, and I only installed it last week... ![Image](https://github.com/user-attachments/assets/be9a0488-2d0f-4e87-97cb-4cbfcdbc3fd3)
GiteaMirror commented 2026-04-11 10:02:30 -05:00
Author
Owner
Copy Link

@Kribbage commented on GitHub (Mar 29, 2025):

well that could explain all the issues I've been having...

<!-- gh-comment-id:2763097342 --> @Kribbage commented on GitHub (Mar 29, 2025): well that could explain all the issues I've been having...
GiteaMirror commented 2026-04-11 10:02:30 -05:00
Author
Owner
Copy Link

@mbecker20 commented on GitHub (Mar 29, 2025):

I see, yes it will aggressively try to reconnect the ws, it needs more of a cooldown

<!-- gh-comment-id:2763102269 --> @mbecker20 commented on GitHub (Mar 29, 2025): I see, yes it will aggressively try to reconnect the ws, it needs more of a cooldown
GiteaMirror commented 2026-04-11 10:02:31 -05:00
Author
Owner
Copy Link

@AnotiaWang commented on GitHub (Mar 29, 2025):

Maybe we could make use of the Page Visibility API or the visibilitychange event, and only try to reconnect when the page is in the foreground

<!-- gh-comment-id:2763104269 --> @AnotiaWang commented on GitHub (Mar 29, 2025): Maybe we could make use of the [Page Visibility API](https://developer.mozilla.org/en-US/docs/Web/API/Page_Visibility_API) or the [visibilitychange](https://developer.mozilla.org/en-US/docs/Web/API/Document/visibilityState) event, and only try to reconnect when the page is in the foreground
GiteaMirror commented 2026-04-11 10:02:31 -05:00
Author
Owner
Copy Link

@AnotiaWang commented on GitHub (Apr 17, 2025):

@mbecker20 I've upgraded Komodo to v1.17.1, seems that the issue is not fixed

<!-- gh-comment-id:2811580054 --> @AnotiaWang commented on GitHub (Apr 17, 2025): @mbecker20 I've upgraded Komodo to v1.17.1, seems that the issue is not fixed
GiteaMirror commented 2026-04-11 10:02:32 -05:00
Author
Owner
Copy Link

@royaltongue commented on GitHub (Apr 29, 2025):

Still seeing this with the latest version released yesterday

<!-- gh-comment-id:2837489454 --> @royaltongue commented on GitHub (Apr 29, 2025): Still seeing this with the latest version released yesterday
GiteaMirror commented 2026-04-11 10:02:32 -05:00
Author
Owner
Copy Link

@cwelsys commented on GitHub (May 1, 2025):

Also experiencing this. I just got IP 🤖banned from my own Komodo instance because of it

<!-- gh-comment-id:2844192292 --> @cwelsys commented on GitHub (May 1, 2025): Also experiencing this. I just got IP 🤖banned from my own Komodo instance because of it
GiteaMirror commented 2026-04-11 10:02:33 -05:00
Author
Owner
Copy Link

@em411 commented on GitHub (May 4, 2025):

If Komodo uses websockets just for sending updates, perhaps we could use Server Sent Events? SSE are unidirectional, simpler, has a built-in reconnection mechanism, and uses fewer resources.

<!-- gh-comment-id:2849111317 --> @em411 commented on GitHub (May 4, 2025): If Komodo uses websockets just for sending updates, perhaps we could use [Server Sent Events](https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events)? SSE are unidirectional, simpler, has a built-in reconnection mechanism, and uses fewer resources.
GiteaMirror commented 2026-04-11 10:02:33 -05:00
Author
Owner
Copy Link

@Buco7854 commented on GitHub (May 4, 2025):

If websocket is already implemented using the visibility change API is probably easier.

<!-- gh-comment-id:2849139308 --> @Buco7854 commented on GitHub (May 4, 2025): If websocket is already implemented using the visibility change API is probably easier.
GiteaMirror commented 2026-04-11 10:02:34 -05:00
Author
Owner
Copy Link

@mbecker20 commented on GitHub (May 4, 2025):

Check 1.17.5

<!-- gh-comment-id:2849485766 --> @mbecker20 commented on GitHub (May 4, 2025): Check 1.17.5
GiteaMirror commented 2026-04-11 10:02:34 -05:00
Author
Owner
Copy Link

@AnotiaWang commented on GitHub (May 5, 2025):

Check 1.17.5

Tested 1.17.5, the reconnecting behavior is much less aggressive now. 👍

<!-- gh-comment-id:2849943267 --> @AnotiaWang commented on GitHub (May 5, 2025): > Check 1.17.5 Tested 1.17.5, the reconnecting behavior is much less aggressive now. 👍
GiteaMirror commented 2026-04-11 10:02:35 -05:00
Author
Owner
Copy Link

@mbecker20 commented on GitHub (Aug 27, 2025):

Should be good since last several releases

<!-- gh-comment-id:3227071875 --> @mbecker20 commented on GitHub (Aug 27, 2025): Should be good since last several releases
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
1.19.0
1.19.1
1.19.2
1.19.3
1.19.4
2.0.0
bug
documentation
done
enhancement
help wanted
info
pull-request
Mirrored from GitHub Pull Request
 question
security
seen 👀
setup
thinking 🤔
ui
v2
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/komodo#2136
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?