Search Issue Tracker
Fixed in 6000.1.0b2
Fixed in 6000.0.X, 6000.1.X, 7000.0.0a8
Votes
1
Found in
6000.0.20f1
6000.0.21f1
Issue ID
UUM-82880
Regression
Yes
The Editor spams the error message "Unexpected transport error from import worker 247. Code=2, error=End of file," causing the Asset Importer to crash
Steps to reproduce:
Three ways to reproduce
First:
1. Create an empty project
2. Close the project and open the Unity Hub and Pass the command line arguments -activeBuildProfile Assets/Settings/BuildProfiles/Mac.asset (Or the windows asset for win users) and -readonly to the project
3. Launch the project and observe the crash
Second:
1. Create an empty project and install the latest mppm 1.3.0 pre-3 and at least unity 6000.0.20f1
2. Go to File- Build Profiles and switch the main editor to any of the build profiles (not the platforms, see photo for example)
3. Once done open Window- Multiplayer - Multiplayer Playmode and launch a virtual player by checking the checkbox next to one of the players
4. Observe to virtual player crashes
Third (2024.10.10):
1. Create a new project with Universal 3D template
2. In Project Settings -> Editor enable Parallel Import
3. Open File -> Build Profiles
4. Select Android/iOS platform and Add Build Profile
5. Switch to the new profile
Actual results:
Crash occurs
(2024.10.10): Unexpected transport error from import worker 247. code=2 error=End of file error spam and asset importer crashes (the editor itself does not crash)
Expected results:
No crash occurs and editor launches with desired build profile + mppm clone editors do not crash when the main editor is set to one of the build profiles
Reproducible with versions:
6000.0.20f1
Not reproducible with versions:
6000.0.19f1
Tested on (OS):
Mac
Windows (On Windows, you might not get errors immediately, but if you restart the project it gets stuck in the loading screen and the project fails to open due to asset importer crashes as well)
Notes:
(2024.10.10) If the project gets into a state where it cannot finish importing the project, the asset importers keep crashing non-stop and adding new crash events. The next time you successfully open a project, all those crash events are sent.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
Resolution Note (fix version 6000.1):
Verified in 6000.1.0b3, tested two different scenarios mentioned in the reproduction and issue did not occur.