You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
What problem did you encounter?
After closing Roblox Studio, the RobloxStudioBeta.exe and RobloxCrashHandler.exe processes (as well as other Wine processes) seem to be still running under Vinegar, causing:
Studio to hog 1.6GB of RAM memory in the background.
Not being able to open Roblox Studio after closing it because of the wineserver instance still running
Errors out with return code 1 and a Wine error 0308:err:esync:esync_init Failed to open esync shared memory file; make sure no stale wineserver instances are running without WINEESYNC.
While this problem can be resolved by running flatpak run org.vinegarhq.Vinegar kill or exiting out of Vinegar through the GNOME "Background apps" menu, it is very annoying to have to do this every single time you want to exit out of Studio.
Acknowledgement of preliminary instructions
What problem did you encounter?
After closing Roblox Studio, the RobloxStudioBeta.exe and RobloxCrashHandler.exe processes (as well as other Wine processes) seem to be still running under Vinegar, causing:
0308:err:esync:esync_init Failed to open esync shared memory file; make sure no stale wineserver instances are running without WINEESYNC.
While this problem can be resolved by running
flatpak run org.vinegarhq.Vinegar kill
or exiting out of Vinegar through the GNOME "Background apps" menu, it is very annoying to have to do this every single time you want to exit out of Studio.System information
The text was updated successfully, but these errors were encountered: