Going from 2018.3 to latest beta

Package manager screwed up. Couldn't find any of the packages I had installed, and it wouldn't show in the menu. Had to remove everything ECS related from the manifest.

Half a dozen prefabs with meshes and materials disconnected.

After it went through importing everything asked if I wanted to reload the scene. Said yes and it looked like it was all done. But knowing better then that I restarted and sure enough this time it re imported all the prefabs. Not a big deal but for general use that's a bit more surprising then it should be.

A hard crash I had in 2018.3 is still there.

An hour in while migrating to the newer Entities packages I hit the following crash. No way to repro, it's a largish project. Do with the stack trace what you will.

========== OUTPUTTING STACK TRACE ==================

0x00007FF6BFA80AC2 (Unity) Component_Get_Custom_PropGameObject
0x000002E51480C903 (Mono JIT Code) (wrapper managed-to-native) UnityEngine.Component:get_gameObject (UnityEngine.Component)
0x000002E514838693 (Mono JIT Code) [C:\Games\aigame\AiClient\Library\PackageCache\com.unity.textmeshpro@2.0.0\Scripts\Runtime\TMPro_UGUI_Private.cs:577] TMPro.TextMeshProUGUI:GetCanvas ()
0x000002E514836A83 (Mono JIT Code) [C:\Games\aigame\AiClient\Library\PackageCache\com.unity.textmeshpro@2.0.0\Scripts\Runtime\TMPro_UGUI_Private.cs:179] TMPro.TextMeshProUGUI:OnEnable ()
0x000002E599F8C848 (Mono JIT Code) (wrapper runtime-invoke) object:runtime_invoke_void__this__ (object,intptr,intptr,intptr)
0x00007FFE4D6DBBCB (mono-2.0-bdwgc) [c:\users\builduser\builds\bltj5ajo\0\vm\mono\mono\mini\mini-runtime.c:2809] mono_jit_runtime_invoke
0x00007FFE4D662252 (mono-2.0-bdwgc) [c:\users\builduser\builds\bltj5ajo\0\vm\mono\mono\metadata\object.c:2919] do_runtime_invoke
0x00007FFE4D66B25F (mono-2.0-bdwgc) [c:\users\builduser\builds\bltj5ajo\0\vm\mono\mono\metadata\object.c:2966] mono_runtime_invoke
0x00007FF6BF971676 (Unity) scripting_method_invoke
0x00007FF6BF96B975 (Unity) ScriptingInvocation::Invoke
0x00007FF6BF9283C2 (Unity) MonoBehaviour::CallMethodIfAvailable
0x00007FF6BF92627D (Unity) MonoBehaviour::AddToManager
0x00007FF6BF9C5C26 (Unity) SerializableManagedRefsUtilities::AwakeInstancesAfterBackupRestoration
0x00007FF6BF92CB9A (Unity) MonoManager::EndReloadAssembly
0x00007FF6BF937E22 (Unity) MonoManager::ReloadAssembly
0x00007FF6BDC513C6 (Unity) ReloadAllUsedAssemblies
0x00007FF6BE1A1C26 (Unity) Application::TickTimer
0x00007FF6BE462333 (Unity) MainMessageLoop
0x00007FF6BE46BD37 (Unity) WinMain
0x00007FF6C0D91FAE (Unity) __scrt_common_main_seh
0x00007FFE99D43DC4 (KERNEL32) BaseThreadInitThunk
0x00007FFE9A283691 (ntdll) RtlUserThreadStart

========== END OF STACKTRACE ===========

 

Also another bug carried over from 2018.3 is fairly often Unity locks up at 0% cpu. The strange thing is that most of the time it's only 100 and something MB and if I expand it in Task Manager it only has the VBCCompiler and one Console WIndow Host. This hits me about every 30 minutes regularly. Nothing in the editor log.

 

Does it also write a crash.dmp file? That would be more useful than the stacktrace only.

 

It probably did, but after lookiung at the trace I realized it was a stale package cache issue, and Unity likely has a clue as to what is going on there.