Oh boy, seems I have to do some reading up on this scenario in git... It seems I cant get this thing to now be a PR for blender-v3.5-release... Afraid I'll have to do from scratch...
testing this with CUDA 12, bisecting unfortunately doesnt give a solution (all tested versions seem fine here)
The buildbot builds show that this got "fixed" between c02ec7440577 and 9719fd69648…
Can confirm, let me check if I can find the commit...
Caused by fb27a9bb983ce74b8d8f5f871cf0706dd1e25051
So #91533 is related, and 917a972b56af103aee406dfffe1f42745b5ad360 is related, too.
CC @ideasman42
OK, out of ideas, but have a look at
blender/blender#100749 blender/blender#88449
they are not functioning there...
That was not it either, so here comes another test:
OK, that was not it, testing another scenario:
Mentioning #38 again
Fine to close it (since I have resolved my pain now 🙂), was just raising awareness My situation might have been special (local build, for some reason this already existing assets folder,…
Should we track this crash report considering it's a regression?
I would think so, yes.