Closed alfonslm closed 1 year ago
This is your first time submitting an issue with UVtools 🥳Please review your issue and ensure that the submit template was followed, the information is complete, and not related to any other open issue. It will be reviewed shortly. Debugging is very important and make the program better. Thanks for contributing and making the software better! 🙌
What I would like to see as an option to avoid this would be to allow the use of a cash to stop the program from crashing especially if it's just for 200mb. The second thing could be to give a warning that the system is running low on ram since it seems like at least in this case that the ram usage increase slightly later in the process and that might be enough to avoid a crash.
An easy thing to start with might be to include a button to enable file compression if an out of memory happens.
Unless you have SWAP disabled / capped, windows manage this quite well, however, is not guarantee that SWAP solve the lack of RAM. Your bottleneck is that you have 40 threads, but only 32GB RAM with half of that usable. By default, UVtools use all power you have and don't care about the core/ram ratio, so it will use +/-40 threads in parallel, that are decompressions/compressions/operations of large bitmaps and take ton of RAM. So, the more cores it uses more RAM you need to sustain that.
To cap that go to Settings and set the "degree of paralelism" under Tasks to a lower value, like 3/4 or ! Other option would be investing in more RAM, but set the degree to a lower value won't kill much of the performance.
That lowered the usage with about 10gb. But getting an error message with that information could be helpful.
System
Printer and Slicer
Description of the bug
My guess for what happened is that a RAM spike crashed the operation after about 10 min when the process was around 90% done.
How to reproduce
Run low on ram
Files
No response