Search Issue Tracker

Fixed

Fixed in 6000.0.60f1, 6000.2.8f1, 6000.3.0b5, 6000.4.0a2

Votes

1

Found in

6000.2.0b3

6000.3.0b1

6000.4.0a1

Issue ID

UUM-107732

Regression

No

AssetImportWorkers crash on compiling ASMDEF while Collab-proxy package is upgrading

-

The Import Worker crashes happen rarely on creating new projects through HUB. There is a special logic which automatically upgrades Collab-proxy package version on project opening, it does that in a wrong time and as result sometimes Import Workers crash. The Compilation pipeline in Workers is reading .asmdef file while it is being upgraded, that happens with these two files: 
{{Unity.CollabProxy.Editor.asmdef}}
{{Unity.PlasticSCM.Editor.Entities.asmdef}}

Steps to reproduce:
1. Simply create new project through HUB from any template. But it happens really rarely 

Reproducible with versions: 6000.0.57f1, 6000.2.3f1, 6000.3.0b1

Reproducible on: macOS, Windows 10, Windows 11
Not reproducible on: no other environment tested

Note: "Fatal Error! Compilation Pipeline: Could not read file" Error is printed before AssetImportWorker crashes

StackTrace:
{code:java}
The AssetImportWorker1 has crashed. Please report a bug with the following Stack Trace:
========== OUTPUTTING STACK TRACE ==================0x00007FFB206FB699 (KERNELBASE) RaiseException
0x00007FFA5C5FA3B9 (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FFA5C5FB0A0 (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FFA5D2A7DDD (Unity) DebugStringToFilePostprocessedStacktrace
0x00007FFA5D2A7159 (Unity) DebugStringToFile
0x00007FFA5CB88065 (Unity) RegisterAssemblyDefinition
0x00007FFA5CFAAFD5 (Unity) ProcessAssemblyAssets
0x00007FFA5CFABD36 (Unity) UpdateScriptCompilationPipelineCaches
0x00007FFA5CEC3964 (Unity) AssetImportWorkerClient::RegisterTransientArtifacts
0x00007FFA5CEC3BE2 (Unity) AssetImportWorkerClient::ReloadScriptingDomain
0x00007FFA5CE9EAF0 (Unity) <lambda_dfe2fdae22f1629f164682966ac9a93e>::operator()
0x00007FFA5CF7F99F (Unity) asio::detail::completion_handler<core::mutable_function<void __cdecl(void)>,asio::io_context::basic_executor_type<std::allocator<void>,0> >::do_complete
0x00007FFA5CF6D161 (Unity) asio::detail::win_iocp_io_context::do_one
0x00007FFA5CF6E46E (Unity) asio::detail::win_iocp_io_context::run
0x00007FFA5CF7E009 (Unity) IOService::Run
0x00007FFA5CEC7B35 (Unity) RunAssetImportWorkerClientV2
0x00007FFA5CEC7BFB (Unity) RunAssetImporterV2
0x00007FFA5C6F9AA0 (Unity) Application::InitializeProject
0x00007FFA5CCDD465 (Unity) UnityMain
0x00007FF71B6A2F2A (Unity) __scrt_common_main_seh
0x00007FFB21517374 (KERNEL32) BaseThreadInitThunk
0x00007FFB22F5CC91 (ntdll) RtlUserThreadStart========== END OF STACKTRACE ===========
 -- for more information, check Logs/AssetImportWorker1.log
{code}

  1. Resolution Note (fix version 6000.4.0a2):

    Fix the logic to install the Unity Version Control package only when downloading a remote repository. This is done from an empty project where the package is not already installed.
    This prevents triggering an *update* of the package on project creation, and the following script reload, which was randomly causing the AssetImportWorker to crash.

  2. Resolution Note (fix version 6000.3.0b5):

    Fix the logic to install the Unity Version Control package only when downloading a remote repository. This is done from an empty project where the package is not already installed.
    This prevents triggering an *update* of the package on project creation, and the following script reload, which was randomly causing the AssetImportWorker to crash.

  3. Resolution Note (fix version 6000.2.8f1):

    Fix the logic to install the Unity Version Control package only when downloading a remote repository. This is done from an empty project where the package is not already installed.
    This prevents triggering an *update* of the package on project creation, and the following script reload, which was randomly causing the AssetImportWorker to crash.

  4. Resolution Note (fix version 6000.0.60f1):

    Fix the logic to install the Unity Version Control package only when downloading a remote repository. This is done from an empty project where the package is not already installed.
    This prevents triggering an *update* of the package on project creation, and the following script reload, which was randomly causing the AssetImportWorker to crash.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.