New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow single app instance per configuration #12083
Conversation
2ad7b4e
to
3bb2d2a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested.
p.s. Also closes #11082
@glassez |
3bb2d2a
to
2524912
Compare
Waiting one more day for @sledgehammer999 review... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@glassez So you're not going to address the manpages in this PR (see my previous comment)?
Sorry, no. |
Ok. |
So is this currently a beta release? Also, how do you use this new feature? I'm guessing this allows you to run two different instances of qbittorrent correct? |
We don't produce betas for minor releases.
Two or more. It produces independent instance for each configuration path/name (you can set it via command line). |
So this commit suggests I'm allowed to have one instance only unless I specify another. |
It creates (should create) different instances per configuration (i.e. profile path + configuration name).
Please provide more details. |
Either via a plain icon in the quick launch area, via autorun I have set up. (If I drag and drop a torrent unsurprisingly no new instance is started) |
Please provide a log message about used Profile path from both instances. |
Seems pretty identical. Apart from the drive letter. (but paths aren't supposed to be case sensitive)
|
@glassez commented on 2020. márc. 26. 20:08 CET:
The CLI doesn't seem much different either, as per Process Explorer:
Not sure why there's a space after the double quote character in the first case. |
They're case insensitive from the Windows filesystem perspective. But they're still different strings so they produce different instance IDs. |
An update: It seems like the secondary instance is broken. It doesn't connect to anything. Added torrents never start, the trackers just show "not yet connected" or something in that vein. And the old torrents don't produce any traffic either, not even after hours. (I accidentally closed the first instance one instead of the duplicate) |
Sure. It uses the same config as the first one so there are conflicts. |
Okay. So it seems to work normally now in 4.2.3. |
IDK if this is related but in recent versions on qB I get multiple instances unintentionally. Say I have qB open and use the browser to add a few new torrents either via magnet or .torrent. Sometimes it will open a second instance that never works. So I need to close and re-add it to the correct instance. Is there a UI way to override this to NEVER allow a second instance? |
Can you check what configuration path is printed in Log in both instances (when it happens next time)? |
Sure no problem. It happens pretty infrequently though. |
Last time it was case sensitivity. I guess it will be something similarly trivial... |
So it just happened and I checked and they both have the exact same path. Which is 6/5/2020 6:53 PM - Using config directory: C:/Users/autostart/AppData/Roaming/qBittorrent/ The second instance showed a bunch of errors about the port/socket/whatever already being in use. I closed both instances and re-opened and the file was there and then started to download. I'm on the latest version of qB and the browser I used to click the link is the new Chromium Edge. |
Does this apply to -nox? I'm trying to run 10 instances of it and using separate config for each. Cheers~! |
Closes #8653.
Closes #11082.