Skip to content
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

[macOS] Crash and Failed to set physical memory (RAM) usage limit #18656

Closed
Oleg-Chashko opened this issue Mar 4, 2023 · 12 comments · Fixed by #19805
Closed

[macOS] Crash and Failed to set physical memory (RAM) usage limit #18656

Oleg-Chashko opened this issue Mar 4, 2023 · 12 comments · Fixed by #19805
Labels
OS: macOS Issues specific to macOS

Comments

@Oleg-Chashko
Copy link

qBittorrent & operating system versions

qBittorrent: 4.5.2
macOS: 12.6.3 (21G419)
Qt: 6.4.2
Libtorrent: 2.0.8.0

What is the problem?

crash report - Archive.zip

Steps to reproduce

No response

Additional context

Screen Shot 2023-03-04 at 17 13 41

Log(s) & preferences file(s)

Archive.zip

@luzpaz
Copy link
Contributor

luzpaz commented May 14, 2023

@Oleg-Chashko can you add error to ticket title so it's less generic, TIA

@Oleg-Chashko Oleg-Chashko changed the title [macOS] Crash [macOS] Crash and Failed to set physical memory (RAM) usage limit May 14, 2023
@JAIrwin
Copy link

JAIrwin commented May 21, 2023

I am also seeing this error message. I haven't had a crash, but I see "Failed to set ... Error code: 22..." at every startup. Going into advanced settings and changing Physical Memory limit and saving adds another error to the log.

qBittorrent: 4.5.2 (64 bit)
MacOS: Ventura 13.3

@ghost
Copy link

ghost commented May 30, 2023

This goes away if you choose libtorrent v1 when downloading or building qbt. Nothing I did after changing this setting would make the error go away including removing the qbittorrent.ini file.

I have made a bug report in for this as well.

@JAIrwin
Copy link

JAIrwin commented May 30, 2023

Shortly after reading your (101John) post my installation offered the update to qbt 4.5.3. The auto-selected update was the libtorrent v1 version - and the error message has gone away. This raises the question of whether the problem is with libtorrent v2 itself, or qbt's implementation of it (at least in the Mac build). It's a shame the qbt team does not have a dedicated macOS developer (as noted on the download page).

@ghost
Copy link

ghost commented May 30, 2023

Here is a comment that may explain why...

I'm sorry, but macOS is outside my competence. As far as I remember, @Chocobo1 added support for setting Working Set limit on Unix systems, without having an exact idea on which systems it would work.

Originally posted by @glassez in #18282 (comment)

It looks like there is a patch available for testing if you want to build the master branch using libtorrent v2

#19022

@JAIrwin
Copy link

JAIrwin commented Jun 2, 2023

It looks like there is a patch available for testing if you want to build the master branch using libtorrent v2

#19022

It looks like you're suggesting I should contribute rather than complain. It's been a while since I've programmed in anything other than Javascript and PHP, so I'd have to re-learn how to build a Mac app from source. Also I have never contributed code to an open-source project so I'd have to learn all the forking, branching, pull-requesting protocol ...

Still - this project does need MacOS contributors ...

@ghost
Copy link

ghost commented Jun 2, 2023

@JAIrwin It took me a lot of time to just learn how to build qBT using a shell script someone else put together.

Even with that script there were issues I had questions about. I am not too familiar with git, and I know how to ask questions which helps.

If you want to give it a shot I can point you in the right direction

@Oleg-Chashko
Copy link
Author

@JAIrwin

Screen Shot 2023-06-06 at 20 31 56

@JAIrwin
Copy link

JAIrwin commented Jun 7, 2023

I can also confirm that I still get the same error with v4.60alpha1. I'm not sure what you meant by "Actions page provided Artifacts", but I am willing to do additional testing if you can clarify what to test.

@xavier2k6 xavier2k6 added the OS: macOS Issues specific to macOS label Jun 8, 2023
@xavier2k6
Copy link
Member

I can also confirm that I still get the same error with v4.60alpha1. I'm not sure what you meant by "Actions page provided Artifacts", but I am willing to do additional testing if you can clarify what to test.

@101John @JAIrwin @Oleg-Chashko Can you test builds from below:
https://github.com/qbittorrent/qBittorrent/actions/runs/5184996254

@xavier2k6 xavier2k6 added the Waiting info Waiting for participants to supply more info/fulfill template requirements label Jun 8, 2023
@JAIrwin
Copy link

JAIrwin commented Jun 19, 2023

@xavier2k6 Sorry to take so long. I randomly selected the last one in the list ([qBittorrent-CI_macOS_GUI=ON_libtorrent-2.0.9_Qt-6.5.0). It included a working .dmg with a qbittorrent.app identifying itself as v4.6.0beta1 (64-bit). Under "software used" it indicates the following libraries:

Qt: 6.5.0
Libtorrent: 2.0.9.0
Boost: 1.82.0
OpenSSL: 1.1.1u
zlib: 1.2.11

It runs on my system (macOS: 13.4 (22F66)) without crashing (at least not immediately) but I still see the error in the log:

6/19/23 7:44 PM - Failed to set physical memory (RAM) usage limit. Error code: 22. Error message: "Invalid argument"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OS: macOS Issues specific to macOS
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants
@luzpaz @JAIrwin @xavier2k6 @Oleg-Chashko and others