utmapp
[Bug] Freeze to death all running VM when trying to add a read-only shared folder that have ">" in its name.... & cannot sucessfully add it.
to be exact when trying to add in the VM settings menu for a non-running vm a shared folder that have ">" in the name, and probably some other digits will share this issue, but no problem adding it in the VM list menu, however there is no option for read-only there in the main VM list menu, only when adding in the VM settings menu, so as stated here https://github.com/utmapp/UTM/issues/6712 it have to be added in read-only from the start.
what happen when you try adding it? when clicking to save settings, it "load forever", if you "Esc" key, it makes the main menu load forever, meanwhile all running VM become frozen and do not respond to anything it seems, not even to shutdown or stop from the utm dropdown menus, it was really important to me not to close all the running VM, but i had no clue how to get out of that loading forever state, closing the main menu and reopening it didn't help either, it was still in the same loading state like it didn't actually restarted the menu, any suggestion what i maybe could have done to avoid closing the running VM in similar scenarios? for future reference.
also i had to force quit eventually, as my system also reported "Your system has run out of application memory." which i don't think i ever had that before? and UTM had in that list 623.50GB (from screenshot) and growing, so i assume its also some data-leak happening along with this bug?
and so, it never actually added the read only folder to the shared list either, tried multiple times while the VM was still closed, so no way to add read-only folder with ">" in the name atm it seems, i usually use stuff like "H>G" for "host to guest", and it was originally as a sub folder along with G>H and others in a global shared folder until now, but when i noticed the read-only option in UTM, i wanted to separate this one on UTM level, so this is a little bugging, but nothing as much of a disaster as forcing me to force-quit my multiple VM that were running.
there, reported, so please, i beg you, that bugs like this in the UI or settings of non-running VM won't do stuff like that for running VM in the future ;_;.
