Search Issue Tracker

Fixed in 2021.2.X

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

Votes

0

Found in

2019.4

2020.3

2021.1

2021.2

2021.2.0a16

Issue ID

1338910

Regression

No

[Editor] Importing a physicsMaterial crashes the Editor inside PhysicMaterial::Reset()

Asset - Database

-

Reproduction steps:
1. Open the attached project "case_1255803-butterflies-e2.zip" or project from Case-1341458
2. If opening the project from Case-1341458, delete the Library folder before opening it

Expected result: the Editor does not crash when importing physicsMaterial
Actual result: Editor crashes on importing physicMaterial

Reproduces on: 2019.4.29f1, 2020.3.12f1, 2021.1.10f1, 2021.2.0a20
Could not test on 2018.4.36f1 due to the project breaking when downgrading

First 5 lines of stacktrace:
0x00007ff7c7616b65 (Unity) PhysicMaterial::Reset
0x00007ff7c77b0092 (Unity) SerializedFile::ReadObject
0x00007ff7c77942a6 (Unity) PersistentManager::ReadAndActivateObjectThreaded
0x00007ff7c77948f1 (Unity) PersistentManager::ReadObjectThreaded
0x00007ff7c7794637 (Unity) PersistentManager::ReadObject

Notes:
-Opening the project subsequently in currently supported Unity streams does not reproduce the crash
-The project "case_1255803-butterflies-e2.zip" was created in 2019.4 and when opening it in 2021.2 it crashes

  1. Resolution Note (fix version 2019.4):

    Fixed in 2019.4.37f1

Log in to vote on this issue

Comments (7)

  1. Liam-C

    Jun 02, 2022 07:52

    I was having this issue in 2019.4.32 (before the fix), only when doing automated scheduled builds via gitlab CI. It started after some physic materials were changed to addressable assets, and changing them back to non-addressable fixed the build crash. It's a potential quick workaround if you can't upgrade your unity version currently.

  2. alexis-sotelo

    Nov 10, 2021 20:17

    Fixed in 2020.3.20f1

  3. shochet

    Oct 26, 2021 15:14

    I was able to work around the problem by renaming the file (it was the only physicmaterial in our project with underscores in the name so that made me suspicious). Perhaps renaming just gave it a new guid or reset something internally - no idea. Maybe that helps somebody else.
    Running Unity 2019.4.31 OSX command line build

  4. shochet

    Oct 26, 2021 14:59

    Just showed up in our Jenkins builds when we updated to 2019.4.31
    Can we get this ported to 2019 LTS?
    Anybody find a workaround?

  5. kookyoo

    Sep 02, 2021 09:11

    Hi.
    We have the issue in 2020.3.16f1. Still not clear what can be causing this but it prevents our automated builds to work. The crash happens on both old or new files. Is there any information about the fix release date ?

  6. tom_opuscope

    Jul 29, 2021 15:27

    Would love a workaround until a fix is pushed.
    We have been stuck on 2020.3.4f1 for two months on our project and we need some fixes that have been pushed meanwhile.
    It also breaks any attempt to build our projects in the cloud since the first import crashes Unity.

  7. thibouf

    Jul 27, 2021 09:51

    Hey it is marked as Fixed , but what about 2019.4.X ?
    Is there any workaround ?

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