Unity editor crashes frequently on Linux+Vulkan after updating GPU drivers

Im still experiencing this issue on nvidia 555.42.02 on my debian machine with HDRP projects that are Vulkan dependent.

Weird fix: Creating a temporary file/folder lets you create new windows for a brief moment of time before crashing again

Can confirm I am also still experiencing this on 555.58.02, URP/Vulkan.

Could you elaborate on what you mean by this?

Has anyone had any success with unity 2022.3.37f1 ? Its suppose to fix…something related to this issues. Tried it on Manjaro, RTX 3060 TI , nvidia driver 550. Still crashes :frowning: . Does not crash when running in opengl mode.

Crashes seem to be less common in 2022.3.37f1, but I am still getting them.

Ok, i cant even start the editor at all, crashes even before any window appear. If i run in opengl it works fine. It also works fine with the older 545 driver.

Unfortunately, crashes still occur on 2022.3.37f1 on my end, same as before.

I’m having this happen as well. It does open sometimes, but the vast majority of the time it closes instantly once the project is loaded. My guess is there’s something specific that ends up making it work, but so far I haven’t been able to identify what.

Edit: Just to offer some data, using the 555.58.02 drivers, I tried starting the Unity Editor (2022.3.37f1) over and over as it crashed on opening every time (flashing a small editor window for less than a second and then closing). After about 10 tries, it opened as expected. This seems to be about average across the past few weeks, where I can get it to open only very occasionally.

I can report that this issue seems to be entirely fixed on my end now, as of Unity 2022.3.40f1.

1 Like

Can confirm: updating to 2022.3.42f1 fixed the issue. Now there are no editor crashes on sub-windows opening when using Vulkan in project.

This error is back again in Unity 6000.0.40f1. (Trying 43f1 now)

What’s odd about it, it worked fine. Then I updated Nvidia drivers from 570.124.04 to 570.133.07 and Unity editor wasn’t able to start anymore with Vulkan. Then I downgraded drivers (massive pain on Linux) but the error persisted.

Nvidia gave me this response:

So please fix Unity. And make it stick! (Somehow! ^^)

BIG SURPRISE! It works in 43f1! Yay!

2 Likes

I recently started getting the same crash very frequently. As in multiple times a day, often in quick succession.

What is annoying is that the crash reporter doesn’t even seem to open and Unity basically just disappears.

I’ve been on 6000.0.40f for a while without issues. But I got a driver update on March 19th:
image

I did upgrade to 6000.0.43f to see if it fixes things but no change for me, still very frequent crashes.

My current setup:
Linux Mint 22.1 Cinnamon
nvidia-driver-550.120-0ubuntu0.24.04.1
Unity 6000.0.43f
URP + Vulkan

Give the latest 570 drivers a chance. I found it’s pretty important with Nvidia and Linux to stay on the bleeding edge of drivers otherwise issues crop up.

Or try to downgrade which is always the safest bet when everything worked fine before.

1 Like

And again with 570.133.07-5.
Downgrading does not help. The only workaround is to force open gl with -force-opengl flag.

I complain on both fronts. Nvidia still says Unity has to fix it. There’s not a single dev response here what’s going on with this. I have this for the 3rd time now. The first time it took ages to work again.

@ivarhill1 Can you give this thread a Linux tag?

edit: Thanks! :slight_smile:

1 Like

I’m still having this problem, any recommendations?

My setup:
Linux Mint 22.1 Cinnamon
nvidia-driver-580-open
Unity 6000.0.31f
URP, Vulkan

Same issue on arch. driver: 470.xx

Hello chaps, you might be seeing problems because of something unrelated to nvidia drivers. Read the
~/.config/unity3d/Editor.log

I have found the following:

Unity:21737): GLib-GObject-CRITICAL **: 23:19:10.216: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
[Project] Loading completed in 7.716 seconds
	Project init time: 				6.474 seconds
		Template init time: 		0.000 seconds
		Package Manager init time: 		0.091 seconds
		Asset Database init time: 		0.171 seconds
		Global illumination init time: 	0.002 seconds
		Assemblies load time: 			1.032 seconds
		Unity extensions init time: 	0.010 seconds
		Asset Database refresh time: 	4.770 seconds
	Scene opening time: 			1.022 seconds
##utp:{"type":"ProjectInfo","version":2,"phase":"Immediate","time":1762125550217,"processId":21737,"projectLoad":7.716050657,"projectInit":6.474081346,"templateInit":0.0,"packageManagerInit":0.090608546,"assetDatabaseInit":0.171078686,"globalIlluminationInit":0.002235482,"assembliesLoad":1.031939247,"unityExtensionsInit":0.010116007,"assetDatabaseRefresh":4.770278147,"sceneOpening":1.021900999}
##utp:{"type":"EditorInfo","version":2,"phase":"Immediate","time":1762125550217,"processId":21737,"editorVersion":"6000.0.61f1 (74a0adb02c31)","branch":"6000.0/staging","buildType":"Release","platform":"Linux"}
Asset Pipeline Refresh (id=a5e7a342b8a1234d58baeb88bd3c47ed): Total: 0.275 seconds - Initiated by RefreshV2(AllowForceSynchronousImport)
Asset Pipeline Refresh (id=4c70f7378ca441c358b65b0a1b686acc): Total: 0.092 seconds - Initiated by RefreshV2(ForceSynchronousImport)
Asset Pipeline Refresh (id=93d5dbd16f388b217a49687060320ea9): Total: 0.139 seconds - Initiated by RefreshV2(NoUpdateAssetOptions)
[Licensing::Client] Successfully resolved entitlement details
Unhandled description string BACKSPACE
Request Asset Garbage Collect because used heap size increased from 232.6 MB to 0.64 GB, exceeding the threshold of 256.0 MB.
Unloading 95 Unused Serialized files (Serialized files now loaded: 0)
Created GICache directory at ~/.cache/unity3d/GiCache. Took: 0.001s, timestamps: [8.004 - 8.005]
Unloading 44 unused Assets / (25.0 KB). Loaded Objects now: 13730.
Memory consumption went from 0.64 GB to 0.64 GB.
Total: 15.551841 ms (FindLiveObjects: 0.683850 ms CreateObjectMapping: 0.122290 ms MarkObjects: 14.572251 ms  DeleteObjects: 0.172890 ms)

Long story short, the problem for me was actually GTK theme all this time.
Driver 580 Unity 6000.61f
The solution to my problem is basically this:

  1. sudo nano /usr/share/applications/unityhub.desktop
  2. Replace with this
[Desktop Entry]
Name=Unity Hub
Comment=The Official Unity Hub (launched with X11 + NVIDIA-stable Vulkan env)
Exec=env GDK_BACKEND=x11 GTK_THEME=Adwaita:dark QT_QPA_PLATFORM=xcb XDG_CURRENT_DESKTOP=GNOME VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json __GLX_VENDOR_LIBRARY_NAME=nvidia /opt/unityhub/unityhub %U
Terminal=false
Type=Application
Icon=unityhub
StartupWMClass=unityhub
Categories=Development;
TryExec=unityhub
MimeType=x-scheme-handler/unityhub;
  1. Launch unity hub as normal and problem should go away