Search Issue Tracker

Fixed in 2020.2.X

Fixed in 2019.4.X, 2020.1.X



Found in




Issue ID




Crash after "[Physics.PhysX] Foundation: Invalid registration detected" errors show up when using Physics.BakeMesh



Steps to repro:
1. Open the project attached by the user
2. Enter Play mode
3. Wait a few seconds until "[Physics.PhysX] Foundation: Invalid registration detected" is shown
4. Close Unity Editor

Expected results: Unity Editor is closed
Actual result: "Fatal Error! GetManagerFromContext: pointer to object of manager 'PhysicsManager' is NULL (table index 9)" window is shown and after pressing Quit button, Unity crashes

Reproducible with: 2019.3.0a11, 2019.3.0f3, 2020.1.0a1, 2020.1.0a16
Couldn't test with: 2019.3.0a10 and older Unity versions due to new Mesh API being unavailable on them

- Physics.BakeMesh is used in multiple background threads

  1. Resolution Note (fix version 2020.2):

    Fixed in 2020.2.0a16

  2. Resolution Note (fix version 2020.1):

    Fixed in 2020.1.0b16

  3. Resolution Note (fix version 2019.4):

    Fixed in 2019.4.4f1

Comments (7)

  1. iamarugin

    Jun 10, 2020 08:16


  2. Micha-Stettler

    May 30, 2020 21:53

    Bug is still there in 2020.2.0a12

  3. Amandin-E

    May 11, 2020 12:30

    I reproduce it with 2020.2.0a10.

    For me, the message "[Physics.PhysX] Foundation: Invalid registration detected" first shows up after I QUIT play mode (I think Physics.BakeMesh doesn't like to be interrupted).

    Once it has happened, the message will show up tons of times as soon as play mode is active.

    The only way to get back to normal is to close Unity, which causes the crash described in this bug report.

    So there are actually 3 issues:
    1) the message should just never show up, even when we exit play mode
    2) if for any reason it shows up, it should be safely restored to a working state so we don't need to close Unity
    3) when we close Unity, it should not crash

    Hope this can help!

  4. TheJavierD

    Apr 24, 2020 14:35

    happens still in 2019.3.10

  5. coidevoid

    Apr 16, 2020 22:37

    2019.3.10f1 didn't fixed it for me.

  6. Kamyker

    Apr 16, 2020 21:04

    started happening to me after some unity inet communication errors

  7. TheJavierD

    Apr 01, 2020 17:29

    this does happen, the unity editor got into this error once, it went away after restarting.

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.