Search Issue Tracker

Fixed in 2021.2.X

Fixed in 2019.4.X, 2020.3.X

Planned for 2021.1.X

Votes

0

Found in

2019.3.0a1

2019.3.12f1

2019.4

2020.1

2020.2

Issue ID

1257558

Regression

Yes

Editor crashes when applying changes to custom ScriptedImporter asset

Scripting

-

How to reproduce:
1. Open the attached project (1257558.zip) using necessary assetpipeline version (use -adb1 or -adb2 command-line arguments)
2. In the Project window open the "SpriteAnimationImporter.cs" script in any script editor
3. Delete line 14 so the script would recompile
4. Return to the Editor
5. In the Project window select the "V00" asset
6. In the Inspector set the "Pixels Per Unit" value to 25 and press "Apply"

Assetpipeline v1:
Reproducible with: 2019.1.0a11, 2019.1.0b4.
Not reproducible with:, 2019.1.0b5, 2019.1.14f1, 2019.2.21f1, 2019.3.0a1, 2019.3.14f1, 2019.4.13f1
Not possible to test: 2018.4.24f1, 2019.1.0a1, 2019.1.0a10, 2020.1.14f1, 2020.2.0f1

Assetpipeline v2:
Reproducible with: 2019.1.0a12, 2019.1.14f1, 2019.2.0a1, 2019.2.21f1, 2019.3.14f1, 2019.4.2f1
Not reproducible with: 2019.1.0a11
Not possible to test: 2018.4.24f1, 2019.1.0a1, 2019.1.0a10

Notes:
1. Tested on Ubuntu 18.0, Windows 10, and OSX 11.0.
2. Only crashes when the object added through the "AddObjectToAsset" method in "OnImportAsset" SpriteAnimationImporter script derives from "ScriptableObject".
3. This issue reproduces on different version depending on assetpipeline version

  1. Response avatar

    Resolution Note (fix version 2021.2):

    This was caused by an interaction between the import process and serialisation. It has been resolved by tightening the restrictions on AssetImportContext::AddObjectToAsset. This function now checks for invalid scriptable objects and errors when attempting to add them to an asset.

    Fixed in 2021.2.0a4

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.