github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #369] barriers.exe / barrierc.exe keep reviving until press 'Stop' button #294

New issue

Closed

opened 2026-05-05 05:58:24 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 05:58:24 -06:00

Owner

Originally created by @JmirY on GitHub (Jul 24, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/369

Operating Systems

Windows10 v1903

Barrier Version

2.3.0-snapshot-057f39c0

Steps to reproduce bug

Run barrier ( Server / Client doesn't matter)
Close GUI (barrier.exe)
Right click barrier icon in system tray and click 'Quit'
By watching task manager, check barriers.exe or barrierc.exe is still running.
Terminate process.
It revives again! then connection established promptly.

Other info

When did the problem start to occur? Always.
Is there a way to work around it? Yes, press 'Stop' before quit.
Does this bug prevent you from using Barrier entirely? Nope.

I think barriers.exe / barrierc.exe should be terminated right after step 3 that I described above.
Perhaps I misunderstood maintainers' intention of program design.
If so, plz fix me😊

Originally created by @JmirY on GitHub (Jul 24, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/369 ### Operating Systems ### Windows10 v1903 ### Barrier Version ### 2.3.0-snapshot-057f39c0 ### Steps to reproduce bug ### 1. Run barrier ( Server / Client doesn't matter) 2. Close GUI (barrier.exe) 3. Right click barrier icon in system tray and click 'Quit' 4. By watching task manager, check barriers.exe or barrierc.exe is still running. 5. Terminate process. 6. It revives again! then connection established promptly. ### Other info ### * When did the problem start to occur? Always. * Is there a way to work around it? Yes, press 'Stop' before quit. * Does this bug prevent you from using Barrier entirely? Nope. I think barriers.exe / barrierc.exe should be terminated right after step 3 that I described above. Perhaps I misunderstood maintainers' intention of program design. If so, plz fix me😊

gitea-mirror

2026-05-05 05:58:24 -06:00

closed this issue
added the
windows

invalid
labels

gitea-mirror commented

2026-05-05 05:58:29 -06:00

Author

Owner

@noisyshape commented on GitHub (Jul 24, 2019):

This is the intended behavior. Closing the GUI frontend is not supposed to affect the background processes. The client and server are also supposed to be restarted when they exit for any reason until the user stops it. On Linux and Mac, the GUI frontend does this. On Windows, the daemon process does this and I think the GUI frontend does as well.

@noisyshape commented on GitHub (Jul 24, 2019): This is the intended behavior. Closing the GUI frontend is not supposed to affect the background processes. The client and server are also supposed to be restarted when they exit for any reason until the user stops it. On Linux and Mac, the GUI frontend does this. On Windows, the daemon process does this and I think the GUI frontend does as well.

gitea-mirror commented

2026-05-05 05:58:31 -06:00

Author

Owner

@JmirY commented on GitHub (Jul 25, 2019):

Thanks for comment @noisyshape 😁

If user right click system tray icon then hit 'Quit'.
it means that user intends to terminate whole process not only for GUI process.
This pattern of interaction is became solid convention for a long time and
there are lots of programs act this way e.g. Slack, Skype, etc...
So barrier should behave in the manner of this to achieve better user experience.

@JmirY commented on GitHub (Jul 25, 2019): Thanks for comment @noisyshape 😁 If user right click system tray icon then hit 'Quit'. it means that user intends to terminate whole process not only for GUI process. This pattern of interaction is became solid convention for a long time and there are lots of programs act this way e.g. Slack, Skype, etc... So barrier should behave in the manner of this to achieve better user experience.

gitea-mirror commented

2026-05-05 05:58:33 -06:00

Author

Owner

@noisyshape commented on GitHub (Jul 25, 2019):

there are lots of programs act this way e.g. Slack, Skype, etc...

Barrier on Windows isn't like those programs. Server and client processes have their own lifecycle and run in the background at boot. It would be strange and unexpected if exiting the frontend stopped those processes.

@noisyshape commented on GitHub (Jul 25, 2019): > there are lots of programs act this way e.g. Slack, Skype, etc... Barrier on Windows isn't like those programs. Server and client processes have their own lifecycle and run in the background at boot. It would be strange and unexpected if exiting the frontend stopped those processes.

No labels

Rows
Columns