The Zulip desktop with 3 organizations connected and after leaving it open for a couple of days, the whole machine starts slowing down noticeably. checked task manager and found multiple Zulip renderer processes sitting there consuming memory — some weren't attached to any visible window at all. only way to fix it was to fully quitting and relaunching the app.
seems to happen when you close to tray and reopen a few times, or when one of the orgs fails to connect on startup and you dismiss the error. those renderer processes just stick around in the background even though nothing is using them anymore.
To Reproduce
configure 2+ organizations in zulip desktop
let one org fail to connect at startup (e.g. server temporarily unreachable), dismiss the error
close the app to tray (not full quit)
reopen from tray
repeat steps 3–4 a few times over the course of a day
check task manager or run ps aux | grep zulip — extra renderer processes have accumulated and are not being cleaned up
also reproducible just by leaving the app running for 2–3 days straight with multiple orgs configured, without doing anything specific.
Expected behavior
when the app is closed to tray or when a failed org connection is dismissed, any renderer processes tied to that session should be properly terminated. after multiple open/close cycles the process count should stay the same as on first launch — not keep climbing.
The Zulip desktop with 3 organizations connected and after leaving it open for a couple of days, the whole machine starts slowing down noticeably. checked task manager and found multiple Zulip renderer processes sitting there consuming memory — some weren't attached to any visible window at all. only way to fix it was to fully quitting and relaunching the app.
seems to happen when you close to tray and reopen a few times, or when one of the orgs fails to connect on startup and you dismiss the error. those renderer processes just stick around in the background even though nothing is using them anymore.
To Reproduce
configure 2+ organizations in zulip desktop
let one org fail to connect at startup (e.g. server temporarily unreachable), dismiss the error
close the app to tray (not full quit)
reopen from tray
repeat steps 3–4 a few times over the course of a day
check task manager or run ps aux | grep zulip — extra renderer processes have accumulated and are not being cleaned up
also reproducible just by leaving the app running for 2–3 days straight with multiple orgs configured, without doing anything specific.
Expected behavior
when the app is closed to tray or when a failed org connection is dismissed, any renderer processes tied to that session should be properly terminated. after multiple open/close cycles the process count should stay the same as on first launch — not keep climbing.