Improvement - better single process enforcement #4755

New issue

Closed

opened 2026-02-21 17:29:20 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-21 17:29:20 -05:00

Owner

Originally created by @leaumar on GitHub (Oct 3, 2016).

I've been having an issue lately that was discussed in detail here: http://portableapps.com/node/43780

tldr: qbt's method of checking if there's already an instance running is easily broken, causing multiple instances to open when you e.g. click .torrent/magnet links in browsers.

Originally created by @leaumar on GitHub (Oct 3, 2016). I've been having an issue lately that was discussed in detail here: http://portableapps.com/node/43780 tldr: qbt's method of checking if there's already an instance running is easily broken, causing multiple instances to open when you e.g. click .torrent/magnet links in browsers.

deekerman

2026-02-21 17:29:20 -05:00

closed this issue
added the
autoCloseOldIssue
label

deekerman commented

2026-02-21 17:29:24 -05:00

Author

Owner

@Chocobo1 commented on GitHub (Oct 4, 2016):

(For devs) This seems ok to replace qtsingleapplication: http://stackoverflow.com/a/28172162
However we'll need to impl IPC ourselves.

@Chocobo1 commented on GitHub (Oct 4, 2016): (For devs) This seems ok to replace qtsingleapplication: http://stackoverflow.com/a/28172162 However we'll need to impl IPC ourselves.

deekerman commented

2026-02-21 17:29:25 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Oct 29, 2020):

This issue has been closed and locked for being too old, and thus either most likely resolved in recent versions or no longer applicable.
If you experience the reported problem or similar in the latest version, please open a new issue report with the requested information in the issue template.

A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression.
Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar.
Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression.

Thank you for your contributions.

@sledgehammer999 commented on GitHub (Oct 29, 2020): This issue has been closed and locked for being too old, and thus either most likely resolved in recent versions or no longer applicable. If you experience the reported problem or similar in the **latest** version, please open a new issue report with the requested information in the issue template. A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression. Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar. Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression. Thank you for your contributions.

deekerman referenced this issue

2026-02-21 22:36:20 -05:00

Optional minimum peer/seed upload speed #12326