[FEATURE REQUEST] Anyway to calculate how much RAM you need ?

[MasterCATZ]

Is your feature request related to a problem?

I have 128gb RAM and kept getting OOM ,
within minutes UVtools would be over 90gb Used and had to close down everything else for UVtools to not crash my desktop

Ubuntu user , multiple times UVTools would just cause entire desktop to reload , (while hollowing / adding infill)
can their be some sort of guard against this ? why can the program not kill its self ?
using UVtools.AppImage

Currently deciding with going 512gb 3200mhz RAM and 1tb 2400mhz RAM

as much as I would love having 1Tb for it to be cost effective I would be taking a 28% performance hit
I rather not spend more than $1500 on more memory
if I knew 512gb would not have a chance of OOM'ing I would rather go that route so my data scrubs are not slowed down
but if UVtools is going to be another memory hog contender with chrome I guess i will jut have to increase the budget

so is their some calculation that can be done based on layers and dimensional size to work out memory usage ?

I was using working with ~250x250x250mm @50um and I can do ~900x900x300mm @25um

Describe the solution you'd like

Program to kill itsself if a set memory usage threshold is reached

Files

No response

[github-actions]

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! 🙌

[sn4k3]

You have a ton of cores, is that 128 the total or it doubles with hyperthreading?
Note that by default UVtools will spawn a task per core, meanwhile if task is late or there are free tasks it will spawn a bit more to compensate. That of course require a lot of ram. Most of operations will take more than a bitmap, sometime three or more bitmap in issue detection. Some memory are only free latter (Not just after task ends).
If by any chance there are a memory leak your system will be killed easy.

My advice is to cut workload in half on UVtools settings, start with 1/2, monitor ram and tune from there.

You can also attach a file here and tell the workflow so I can check it.
Infill operation does take alot of ram...

UVtools is going to be another memory hog contender with chrome

Chrome has no chance here 😁

Program to kill itsself if a set memory usage threshold is reached

I think it's possible to add a limiter that cancels the current operation (If supported)

[sn4k3]

Implemented a limiter, please test it.