-
Notifications
You must be signed in to change notification settings - Fork 119
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
Process killed #4
Comments
Hey, first, it would be better if you used the shell script (run_fastsurfer.sh). The memory problem is most likely caused by the batch size (it is 16 by default). You can change it with the flag --batch (or --batch_size for the python script) e.g. set it to 1 to see if the problem goes away. Best, |
This is probably resolved. In case reducing the batch size did not solve it, we can reopen. |
This fixed it, thanks! |
Hello! First of all, thanks for pushing this out. I've been testing this on my end directly with the
run_fastsurfer.py
file. Unfortunately the process gets killed and I'm not sure why. I do suspect it may have to do with memory.This is running in a Python 3.6 environment on a system with Ryzen 2700x, GTX1080 and 16 GB RAM.
EDIT: Upon further investigation, it is indeed an out of memory error:
That translates to ~32 gigabytes of memory that the script requested. I'll try this on a system with larger memory.
The text was updated successfully, but these errors were encountered: