Search Issue Tracker

Fixed in 3.1.4

Votes

3

Found in [Package]

3.1.1

Issue ID

1227166

Regression

No

Crash on RtlEnterCriticalSection when importing large number of .psb files

Package: 2D PSD Importer

-

How to reproduce:
1. Open link in edit and download attached project "Case_1227166"
2. Open the downloaded project

Reproducible with: 1.0.0-preview.1 (2018.4.19f1), 2.1.0 (2019.3.6f1), 3.1.1 (2020.1.0b2, 2020.2.0a3)
Not reproducible with: 2017.4.38f1 (Package Manager not available)

First lines of the stack trace:
0x00007FFFE6439C90 (ntdll) RtlEnterCriticalSection
0x00007FFFE6439AD0 (ntdll) RtlEnterCriticalSection
0x00007FF632AD1EB7 (Unity) AssetResolveTracker::Track
0x00007FF632AF7452 (Unity) AssetResolver::CalculateAssetState
0x00007FF632B2E3FD (Unity) EditorAssetResolver::ResolveAsset
0x00007FF632AEF643 (Unity) ResolveArtifactV2

Notes:
1. Crashes while importing large amounts of .psb files
2. Importing these files one by one does not crash, but it does crash when reimporting them all at once
3. Importing these files causes a memory leak
4. Crashes display drivers, sometimes they can no longer start along with Windows after this and instead, the Microsoft Basic Display Driver starts
5. On Mac keeps consuming Memory until the System runs out of Application Memory

Comments (2)

  1. bearcoree

    Mar 17, 2020 19:04

    This issue leads to cloud build being stuck indefinitely, because cloud build deletes the library when a build fails (this is intended and correct behavior otherwise).

    That leads to us currently being unable to use cloud build at all.

  2. Getsumi3

    Mar 13, 2020 07:18

    Reproduced is Unity 2018.4.7f1 with 1.0.0-preview.4

    Crashes while importing more than 10 .psb files at the same time (checked on Mac and Windows).

Add comment

Log in to post comment