AllBugsFeaturesChangelogBountiesSearchNew post
Sign in with Fluxer
Bugs

Fluxer Canary processes not terminating after app close

(#3955) Bug Open: Confirmed Priority: P1 desktop performance
by Adam Novagen edited

Reproduction steps

  1. Fully launch Fluxer Canary
  2. Have system tray icon entirely disabled
  3. Leave app open for any amount of time
  4. Close app

Expected behaviour

Application should close as normal and all related processes should terminate

Actual behaviour

Application window closes, but multiple Fluxer Canary processes remain running and will not terminate after any amount of time, even overnight. Fluxer cannot be relaunched until these processes are forcibly closed via Task Manager (failure to launch is how this issue was initially discovered). Re-enabling the system tray icon and using "Quit Fluxer" from the icon context menu will still successfully close the app as expected.

Build information

Canary Desktop 2026.1012.194217, Web 2026.1012.194217, Windows 10 10.0.19045 (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US

Evidence

d9163b4353259f866fd4e5c61593b921.jpg 561bae64be2fa39114e00049725bf72c.png

9 comments

Sign in with Fluxer to comment and vote.
Comment by Fullest
FullestReviewer 1 vote
Status changed from Needs triage to Confirmed
CR: Canary Desktop 2026.1015.145307, Web 2026.1015.210822, Linux 7.2.10-200.fc44.x86_64 (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US
Permalink
Comment by Dinosaur Gnatalie
Dinosaur Gnatalie 2 votes 4 replies
I'm experiencing this with both Stable and Canary desktop clients on Nobara Linux. Canary closes properly if I have "Show system tray icon" enabled in the App settings > Linux app settings. However, Stable won't close properly no matter if that is enabled or disabled. Closing the app(s) closes the window and sometimes removes the tray icon, but it remains active in the System Monitor, where I have to quit the app before I can reopen it. (Note: No screensharing or VC activity.) Stable Desktop 2026.1013.200953, Web 2026.1013.223959, Linux 7.2.10-200.nobara.fc44.x86_64 (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US Canary Desktop 2026.1013.201015, Web 2026.1014.5142, Linux 7.2.10-200.nobara.fc44.x86_64 (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US
Permalink
Comment by Adam Novagen
Adam Novagen OP1 vote 3 replies
Ooh, nice catch! I tested this and found the same behavior on my Windows problem PC: re-enabling the system tray icon and "close to system tray," then using the system tray icon to select "Quit Fluxer," will close the program successfully and stop all processes immediately. As soon as I disable the system tray icon again, the processes fail to terminate when the program is closed.
Permalink
Comment by Fullest
FullestReviewer 1 vote 2 replies
I can reproduce this as well. Could you edit your report to reflect these new findings, and also remove the Win10 tag since this seems to affect other platforms? I can confirm this once that's done.
Permalink
Comment by Adam Novagen
Adam Novagen OP1 vote
Report has been updated, let me know if any further edits or information is needed.
Permalink
Comment by Fullest
Fullest 1 vote 1 reply
Just a hunch, but this might be related to 3388.
Permalink
Comment by Adam Novagen
Adam Novagen OP1 vote edited
I have not personally encountered the behavior described in that report, and the Canary processes exhibit the behavior described above even if no screen share or voice call is started/connected for the duration of the program being open.
Permalink
Comment by Adam Novagen
Adam Novagen OP1 vote edited
Program has been tested on another Windows 10 PC, and the issue does NOT occur on the second machine. Hardware configurations are very different, both PCs are running Windows 10 but not the same build version. Details per machine can be provided if needed. I plan to test with additional computers in the next few days. Second PC build info: Canary Desktop 2026.1013.201015, Web 2026.1013.223957, Windows 10 10.0.19045 (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US (Original PC is still presenting the described issue after Canary update, build info is identical to second PC: Canary Desktop 2026.1013.201015, Web 2026.1013.223957, Windows 10 10.0.19045 (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US)
Permalink