Bug 2019.3 regressions / bugs that occur often but not sure how to reproduce

Another error I regularly get since a couple of betas without being able to reproduce it is the one below. Only restarting the editor helps in this case. Anybody know what this one is about?

 

@LeonhardP was able to record another thing similar to (4), this time the Transform Gizmo getting stuck.

 

Another one with AssetDatabase V2. Sometimes spamming the console with thousands of errors.

 

@LeonhardP was able to record a video of the above and can verify that once it's broken the above exceptions are happening on every Unity window focus.

 

The 2019.3.0f1 version of the editor is crashing randomly at random intervals doing random things.

1. Unity sometimes crashes when leaving it for a few minutes.
2. Unity sometimes crashes when compiling shaders inside AND outside of play-mode
3. Unity sometimes crashes when moving around in the scene
4. Unity sometimes crashes when fiddling with either Project or HDRP specific settings
5. Unity sometimes crashes after using it for a long time, probably connected to previous crash reasons

The crashes does not produce a crash report or even notify me that the editor has crashed, it just shuts the entire process down.

When restarting unity it reverts back all changes made since unity had started, regardless of having saved the scene and or project before the crash.

I am also getting this error when starting unity, but this does not seem to be a known issue:

Spoiler

Shader error in 'HDRP/Lit': pasting formed ')Array', an invalid preprocessing token; use of undeclared identifier 'unity_BuiltinsUNITY_WORLDTOOBJECTARRAY_CB' at Packages/com.unity.render-pipelines.core/ShaderLibrary/SpaceTransforms.hlsl(12) (on d3d11)

Compiling RayTracing program with INSTANCING_ON STEREO_INSTANCING_ON _NORMALMAP_TANGENT_SPACE
Platform defines: UNITY_ENABLE_REFLECTION_BUFFERS UNITY_USE_DITHER_MASK_FOR_ALPHABLENDED_SHADOWS UNITY_PBS_USE_BRDF1 UNITY_SPECCUBE_BOX_PROJECTION UNITY_SPECCUBE_BLENDING UNITY_ENABLE_DETAIL_NORMALMAP SHADER_API_DESKTOP UNITY_LIGHT_PROBE_PROXY_VOLUME UNITY_LIGHTMAP_FULL_HDR

Spoiler

Shader error in 'HDRP/Unlit': pasting formed ')Array', an invalid preprocessing token; use of undeclared identifier 'unity_BuiltinsUNITY_WORLDTOOBJECTARRAY_CB' at Packages/com.unity.render-pipelines.core/ShaderLibrary/SpaceTransforms.hlsl(12) (on d3d11)

Compiling RayTracing program with INSTANCING_ON
Platform defines: UNITY_ENABLE_REFLECTION_BUFFERS UNITY_USE_DITHER_MASK_FOR_ALPHABLENDED_SHADOWS UNITY_PBS_USE_BRDF1 UNITY_SPECCUBE_BOX_PROJECTION UNITY_SPECCUBE_BLENDING UNITY_ENABLE_DETAIL_NORMALMAP SHADER_API_DESKTOP UNITY_LIGHT_PROBE_PROXY_VOLUME UNITY_LIGHTMAP_FULL_HDR

I am also not able to build my game, the standalone player is crashing every time we try to run it. It seems to be crashing at startup so nothing has loaded or anything.

This is making 2019.3.0f1 pretty un-usable atm for me at least. The weird thing I noticed is that Unity is crashing much more frequently on my RTX Laptop compared to my colleagues GTX stationary machine.

 

Perhaps some of the crashes are due to using Error Pause like they were for me: https://forum.unity.com/threads/2019-3-0f1-is-unusable.785804/#post-5238017

 

@LeonhardP this project has been reimported a couple of times during the 2019.3 beta cycle (last on the version we're on - 2019.3.0b11), and usually there's no errors afterwards, but they keep coming back, like in this case. They were not there end of last week, but started on monday after reverting a change in git, thus why I think it's related to AssetDatabase not properly cleaning up.

Having to reimport the AssetDatabase is considered a bug (at least if I believe the warning message before doing that), I can try it, but again, this project has been reimported on that machine on 2019.3.0b11 already when that came out.

 

I have surprisingly enough not had Error Pause active during this entire project. This is something I usually do but yeah this is not the problem.

 

@LeonhardP I'd like to point your attention to another bug that I find pretty serious but QA has now closed. It happens occasionally across various projects.
I don't know how to reproduce but was able to record a video of the behaviour: (Case 1201935) [Editor Regression] Window Layout Broken, Can't Rename Objects, Can't Use Input Fields

 

This still happens on 2019.3.0f4, but not sure how to reproduce. It seems to happen when either moving or renaming asmdef files and/or changing their dependencies.



This message is a "dead end" - it requires Editor restart to fix (can't be cleared from Console) and then is gone.

 

I was playing around with 2019.3.0f4 and ran into a weird bug where the Inspector stopped showing the properties of the selected GameObject.

I have no idea how to reproduce the issue, but I recorded a video to proof this issue really exists.

What you can see in the video is that while I select various different GameObjects in the Hierarchy, none of them show up in the Inspector window. The Inspector isn't locked, I toggle this in the video too just to be sure.

The problem vanished once I exited play mode. ¯\_(ツ)_/¯

(Case 1210942) 2019.3: Inspector does not update (random issue)

 

This issue has affected me in 2019.2 and 2019.1 as well, but I can't figure out how to reproduce it.

 

I wonder if this is the same issue as shader graph. If you turn some node to propety, SG gets locked and you can't change any other property.

 

Wait, the crash reporter does not upload crash dumps or crash call stacks? It's amazing when you get detailed repro steps, sure, but in my experience in game and software development only a minority of users are able and willing to provide such reports. Many bugs can be identified with a crash dump or a detailed callstack, and you can have an idea of how widespread a bug is by aggregating callstacks on a database. Saved my life in many projects.

 

... and the QA team will nonetheless just close the bug as "non reproducible" and has told me on repeat occasions that I should not submit bugs that I don't have perfect reproduction steps of.