Search Issue Tracker

Fixed in 2022.1.X

Fixed in 2019.4.X, 2020.3.X, 2021.1.X, 2021.2.X

Votes

4

Found in

2018.4

2019.4

2020.3

2020.3.1f1

2021.1

2021.2

Issue ID

1324536

Regression

No

Editor crashes with out of memory while importing a lot of assets (mostly textures) at once, on Windows/DX11

Asset - Database

-

The issue seems to be that during a texture import, video memory usage keeps on rising, eventually runs out of GPU VRAM, starts to use system memory, and eventually can run out of that too. Seems specific to Windows & DX11 graphics API.

How to reproduce:
1. Open the attached project

Reproducible with: 2018.4.33f1, 2019.4.24f1, 2020.3.1f1, 2021.1.0b12, 2021.2.0a10

Notes:
- The textures inside the project generate a 20+GB Library folder
- The project opens without a crash when opening it again

  1. Resolution Note (fix version 2022.1):

    Fixed in 2022.1.0a2

  2. Resolution Note (fix version 2021.1):

    Fixed in 2021.1.17f1

  3. Resolution Note (fix version 2020.3):

    Fixed in 2020.3.20f1

  4. Resolution Note (fix version 2019.4):

    Fixed in 2019.4.32f1

Log in to vote on this issue

Comments (15)

  1. rekenechard

    Aug 25, 2021 03:11

    We just updated from 2019.3 to 2020.3.15f2 and half our people are having what seems like this issue. The other half are not having any issues. We have found no correlation for hardware or software that connects the failing or the passing systems yet. Any input on this would be great to have.

  2. TheHartPony

    Aug 15, 2021 22:50

    From my experience, even opening the project again will cause it to crash, unless my project is that large that it will crash many times before it actually opens.

  3. TheHartPony

    Aug 15, 2021 22:45

    This is a serious issue that can stop people of even small-medium size projects to open their project, its also not fixed in 2021.2.0b7. I can't upvote it either.

  4. gonen_unity

    Aug 15, 2021 06:42

    Its not fixed in 2020.3 , why can't I vote up on this?

  5. nehvaleem

    Aug 13, 2021 10:13

    how is it possible that this is "planned for 2020.3.X" when it was marked as fixed in all versions on 28/07/2021?

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