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

Fishtest displays memory and config file error after using Lenovo Vantage memory cleanup; restart already tried #2153

Open
kunningKing11 opened this issue Dec 20, 2024 · 4 comments

Comments

@kunningKing11
Copy link

kunningKing11 commented Dec 20, 2024

Fishtest has worked fine for me for a while, until I used Lenovo Vantage's memory cleanup feature (while fishtest was not running). Since then, every time I have tried to open fishtest it shows an error about reserved memory and it says the config file is not written (even if it is).

I don't know if this helps, but here is the system info:
Intel Core Ultra 185H
64 GB RAM
NVIDIA RTX 4070 Mobile Graphics Card (8 GB)

Note: I have tried recreating the worker multiple times and it still doesn't work. I have converted the .config file to a .txt file so it can be uploaded.

fishtest.txt
image

@Disservin
Copy link
Member

I deleted your fishtest.txt file since it included your password... please change it nonetheless

@vdbergh
Copy link
Contributor

vdbergh commented Dec 22, 2024

Everything seems to be fine with your configfile. I guess something is wrong with how the worker determines the amount of memory. This is the powershell command the worker uses

(Get-CimInstance Win32_OperatingSystem).TotalVisibleMemorySize*1024

Perhaps you can try it directly?

@kunningKing11
Copy link
Author

Everything seems to be fine with your configfile. I guess something is wrong with how the worker determines the amount of memory. This is the powershell command the worker uses

(Get-CimInstance Win32_OperatingSystem).TotalVisibleMemorySize*1024

Perhaps you can try it directly?

It works fine when I try it (it outputs 68,305,674,240) but Fishtest still doesn't work.

@vdbergh
Copy link
Contributor

vdbergh commented Dec 22, 2024

Hmm. That is strange. Can you rename the config file and restart the worker? Then it will create a new config file (it will ask for your username and password again, if you don't provide it on the command line).

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

No branches or pull requests

3 participants