Hey Garuda community,
sharing my own experience with Wine. I remember, it was even more dire at the beginning of this year. I am honestly surprised in a positive way, the kernel now has killed processes when the system has got overloaded. It fixes the overload issue. Fortunately, I did not lose anything.
It prevented me from choking off the system with hard power off. It got seriously overloaded, filling up 32GiB of my RAM.
The simple thing I did: open a windows URL link from my backup drive. Wine f*ks up at this. It will run in the background, invisible. It opened over 2500 processes (literally processes) and renders the system unusable after some time (filled up RAM). This is not a singularity. I avoid using Wine for anything than playing games. (Which works incredibly well by the way, I am so grateful!)
Wine, when invisibly starting itself upon pressing on Windows files, is a real danger.
Any safety suggestions to prevent Wine from running amok? I would think of removing Wine from any default application mime bindings.
Just as a side note, I had a similar situation with specific file interactions (maybe KIO stuff) in Dolphin some time ago, but in the contrary to Wine (which occupies all or most CPU cores) fortunately, it only placed a constant 100% on one processor. I think it went away when Dolphin was terminated. Maybe this issue has been fixed.
Hope you had a good and safe weekend.
Regards, Elmar