Search Issue Tracker
Fixed
Fixed in 2023.2.20f1, 6000.0.1f1, 7000.0.0a1
Votes
8
Found in
6000.0.0b15
7000.0.0a1
Issue ID
UUM-64341
Regression
No
"Unexpected transport error from import worker 0" error is thrown when importing an asset
Reproduction steps:
1. Open the attached “ASDQWE” project
2. Import an asset into the project
3. Observe the Console Window
Expected result: No error is thrown
Actual result: "Unexpected transport error from import worker 0. code=10054 error=An existing connection was forcibly closed by the remote host." error is displayed
Reproducible with: 2023.2.5f1
Reproducible on: Windows 11 (user’s)
Not reproducible on: No other environment tested
Notes:
- The issue could not be reproduced locally by CQA
- The user reported that the issue does not reproduce constantly
- The user reported that the issue could be reproduced on different setups
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 6000.0.1f1):
Fixed the crash of asset import worker that could happen due to many code changes and domain reloads within the worker
Resolution Note (fix version 2023.2.20f1):
Fixed the crash of asset import worker that could happen due to many code changes and domain reloads within the worker