Upgrading Unity Project - es3postprocessor crash

[Ell223]

I am also having this exact issue after upgrading to 2021.2.8f1. It's something to do with the Easy Save manager references. If I turn on Auto add references, I get a crash on play. If I turn this off and manually hit refresh in the manager, crash. But I also cannot recreative it in a new project.

This is the stack trace:

Code: Select all

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

0x00007FFB0E1FC496 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\external\bdwgc\mark.c:1379] GC_push_all 
0x00007FFB0DF8709B (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\boehm-gc.c:787] mono_push_other_roots 
0x00007FFB0E1F9B3A (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\external\bdwgc\mark.c:457] GC_mark_some_inner 
0x00007FFB0E1F99EB (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\external\bdwgc\mark.c:522] GC_mark_some 
0x00007FFB0E202CAD (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\external\bdwgc\alloc.c:832] GC_stopped_mark 
0x00007FFB0E203638 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\external\bdwgc\alloc.c:580] GC_try_to_collect_inner 
0x00007FFB0E1F45D5 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\external\bdwgc\alloc.c:1224] GC_gcollect 
0x00007FF77499D87D (Unity) CleanupAfterLoad
0x00007FF7749EE39C (Unity) LoadSceneOperation::CompletePreloadManagerLoadSceneEditor
0x00007FF7749EEF2B (Unity) LoadSceneOperation::IntegrateMainThread
0x00007FF7749F2B21 (Unity) PreloadManager::UpdatePreloadingSingleStep
0x00007FF7749F30FF (Unity) PreloadManager::WaitForAllAsyncOperationsToComplete
0x00007FF775BAD0D2 (Unity) EditorSceneManager::RestoreSceneBackups
0x00007FF7758C9FC5 (Unity) PlayerLoopController::EnterPlayMode
0x00007FF7758D933A (Unity) PlayerLoopController::SetIsPlaying
0x00007FF7758DC65D (Unity) Application::TickTimer
0x00007FF775D1803A (Unity) MainMessageLoop
0x00007FF775D1C90B (Unity) WinMain
0x00007FF77702D942 (Unity) __scrt_common_main_seh
0x00007FFB71C17034 (KERNEL32) BaseThreadInitThunk
0x00007FFB737E2651 (ntdll) RtlUserThreadStart

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

[Ell223]

I think I have found the issue. There appears to be some kind of conflict with Easy Save and Rewired's Input Manager. If I remove Rewired Manager from the scene, no crash. If I add it back in, crash. I have managed to replicate this in a new project also. Is there a way for me to exclude generating references to anything related to the Rewired object as a workaround? Can also send you the replicated project if necessary, although to replicate it you simply just need to have both objects in the scene and hit refresh.

Will let you know if I figure anything else out.

[Joel]

Hi there,

If you’re able to send us the project which replicates it that would be appreciated. Easy Save’s referencing simply adds references to a list, so the issue is likely to be at Rewireds or Unity’s rather than ours, but happy to confirm this.

There would be no way of excluding them from automatic referencing, so in this case you would need to disable it and manually add references.

All the best,
Joel

[Ell223]

Thanks, send you a PM with the project. I've worked around it for now by just adding a "blacklisted references" to the ES3ReferenceMgr, that just checks if the objs is in this list and doesn't add it if it is.

[robotSmith]

Hello, I have the same problem where I'm manually refreshing the referencing and it crashes with "Unexpected mark stack overflow". I also have Rewired. Have you been able to confirm where is the issue coming from?

MarkIssue.png (22.78 KiB) Viewed 1686 times

[robotSmith]

Thanks, send you a PM with the project. I've worked around it for now by just adding a "blacklisted references" to the ES3ReferenceMgr, that just checks if the objs is in this list and doesn't add it if it is.

And Ell223, would you be able to share the snippet of code you added? It would be greatly appreciated!

[Joel]

Thanks, send you a PM with the project. I've worked around it for now by just adding a "blacklisted references" to the ES3ReferenceMgr, that just checks if the objs is in this list and doesn't add it if it is.

And Ell223, would you be able to share the snippet of code you added? It would be greatly appreciated!

I can also send you an update version of Easy Save (modifying source files is not recommended) if you remind me of your invoice number via PM, which looks less deeply for references. The issue appeared to be that the asset in question had an extremely wide serialisation tree, but reducing the referencing depth mitigated this.

All the best,
Joel

[robotSmith]

Awesome, sent! The workaround that I had from reading this was to remove the Rewired Manager, generate the References, and then add the Rw. Manager again.