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

  1. 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

  2. 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

Log in to vote on this issue

Comments (11)

  1. rganin_unity

    Oct 05, 2024 05:28

    Issue still exists in 6000.0.21f1, deleting Library folder doe snot help.

  2. elsante

    Oct 04, 2024 01:11

    This issue persists in Unity 6000.0.21f1, but I fixed it by deleting the Library folder. Hope this can help someone.

  3. YANGJOONWOO

    Sep 30, 2024 05:55

    This issue persists in 6000.0.21f1

  4. jussituomi

    Sep 24, 2024 14:06

    This issue still happens in 6000.0.20f1.

  5. xavier-ateo

    Sep 24, 2024 08:47

    This issue persists in 6000.0.20f1

  6. duckreaction

    Aug 06, 2024 08:37

    Still have the issue with 2023.2.20f1.

  7. Eran-Yaacobi

    May 10, 2024 23:50

    Looking at the crash log it shows that the line that causes the crash is this one (from the xNode asset):
    XNode.NodeGraph graph = AssetDatabase.LoadAssetAtPath (assetpath, typeof (XNode.NodeGraph)) as XNode.NodeGraph;

    This is inside a class derived from AssetModificationProcessor, in the OnReloadEditor method.
    I've added logs around that line, and it seems that the asset that causes the issue is the same file every time. However, sometimes it actually succeeds in processing that asset without any errors. The asset also loads properly in Unity (regardless of whether the error occurs or not) and works fine. So it doesn't seem that there's any issue with the asset itself.

  8. Eran-Yaacobi

    May 10, 2024 23:14

    I'm having the same issue even after upgrading to Unity 2023.2.20, which suggests that the error is not fully fixed.

    On my computer (and two others with the same project), at some point the error starts to show every 40 seconds or so, along with Unity taking up 30GB every time (which really hurts performance). The issue does not go away even on restarting Unity, but does go away for a couple of days (though sometimes less - even just a couple of hours) on 'Reimport all', which suggests that the source of the error is that something causes the asset database to become corrupted.

  9. spiney199

    Feb 29, 2024 12:02

    I believe I have more info on the cause of this here: https://forum.unity.com/threads/constant-unexpected-transport-error-from-import-worker-errors.1546922/

  10. zenbin3d

    Feb 21, 2024 14:58

    Same here! Supper annoying! Happens almost every 50 seconds.
    I think it's related to Project Settings -> Editor -> Asset Pipeline - Parallel Import setting.

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.

Latest issues

See all new issues