Search Issue Tracker

Fixed in 2021.1.X

Fixed in 2020.2.X



Found in






Issue ID




Texture Assets are reimported when the launched Editor is recovering from an unexpected close if there were compilation errors

Asset - Database


How to reproduce:
1. Open user-submitted project (
2. Open the Assets/Scripts/BreakTheTextures.cs script
3. Uncomment the 'broken!' line and let the Editor recompile scripts
4. Force-quit the Editor by ending the task
5. Launch the project again and note the loading process

Expected result: the textures are not reimported because nothing changed
Actual result: the textures are reimported

Reproducible with: 2019.2.0a9, 2019.4.5f1, 2020.1.0f1, 2020.2.0a18
Not reproducible with: 2018.4.25f1, 2019.2.0a8

Notes: reproducible with ADBV1 and ADBV2

  1. Resolution Note (fix version 2021.1):

    The issue is the following:

    1. User project successfully loads (Domain A)
    2. User introduces compile error, domain is NOT reloaded (Domain A still loaded)
    3. Editor is restarted
    4. Partial domain (Domain B) is now loaded, but certain dependency checks depend on the full domain to be loaded (i.e. the postprocessorVersionHash)
    5. Once compilation errors are fixed during Safe Mode, domain is loaded (Domain A) and dependencies match so nothing is imported
    6. Without Safe Mode we would see this behaviour though.

    Recommended workaround:
    1. Don't shut down the editor when there are Compile Errors present if not on an Editor Version with SafeMode

  2. Resolution Note (fix version 2020.2):

    Fixed in 2020.2.0b3 by the introduction of Safe Mode, which is prompted when the project has script compilation errors

Comments (2)

  1. gbedufiva

    Jul 21, 2020 07:50

    GBEDUFIVAJUL 21, 2020 07:33

  2. lekanvictorc

    Jul 21, 2020 06:39

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.