remesh modifier slider is too easy to crash blender

Maybe a soft limit would be the solution in this case. You can't go lower than a specific value with the slider, but you can do it typing. As it happens for example in the node Color Mix > Factor slider, where you can go over 1 but just typing

Blender's value sliders contain Min/Max values and the ability to specify if the user can enter their own value manually. Rather than reconstructing the UI, the Min/Max should be set to something realistic for a recommended spec system. (So the user can manually enter a different value for their needs)

this may be a bug, it goes.

0.03

0.02

0.01

0.0001

instead of 0.0001 it should be 0.009

My whole computer is dead right now because of this. Waiting in vain for task manager to spare me a hard restart.

We really need a safeguard for accidentally dragging to low. Pressing r and then dragging toa (what seems) sensible size only to be greeted with a screeching halt to the system and if you're lucky suddenly 55.000.000 faces for what was supposed to be a ~ 30.000 face increment for the sculpt. The new limit of 0.0001 as bottom is appreciated but not enough by itself.

If Blender detects that the remesh action is going to create more than a dedicated limit (maybe even in the settings) it should pop up a warning: "You sure you want to do this? This might crash your system." with the option to suppress the warning for this session.

No need to suppress it forever since the option in the settings can be set to a ridiculously high amount if desired. But we need a limit. Especially for graphics tables it's too easy to accidentally drag the last few pixels between sensible scale and oblivion. The above is an actual example.

I wish other modfier can haddle this even better without crashing.

An alternative that would apply to any "heavy" functions:

Why not have the UI listening for input on a separate thread with a higher priority than other blender threads? Then if you pressed/held ESC, Blender could at least have the option to try to gracefully abort the operation in question.

But general rule: do not drag sliders on sensitive values ever! Input exact number N or it`s fraction N/4 Buttons like x*2 or x/2 may be nice in this case. But I wold prefer to keep slider and float value.

agree, for such values there should be softlimits and half-steps between decimal places like

0.2 0.1  >0.05<
0.04 0.03 0.02 0.01 >0.005<
0.006…

YES. If it goes below 0.1, the next increment is too much and generally hangs. It could reduce the division by half of the amount to decrease. It could also offer a warning icon which when the user hovers over this, there's a note to explain why it's happening.