Search Issue Tracker

Fixed in 2018.3.X

Fixed in 5.5.X, 5.6.X, 2017.1.X, 2017.2.X, 2018.1.X, 2018.2.X

Votes

334

Found in

5.6.0b5

2017.1.0f3

Issue ID

873467

Regression

Yes

Unity throws out Fatal Error: Callback registration failed kMaxCallback

Themes

-

Unity throws out Fatal Error: "Callback registration failed kMaxCallback" after working with the project for 30 minutes or more. It appears randomly.

Steps:
1. Actively use Unity for more than 30 minutes

Actual: Unity continues to work
Result: Unity crashes with Fatal Error.

Reproducible with: 2017.1.4f1, 2017.2.3p1, 2017.4.4f1, 2018.1.3f1, 2018.2.0b6

Note:
Reproduced on macOS, Windows, Linux.
Bug Report window does not appear.
Scene files are not restored after reopening Unity so all not saved Scenes are lost.

  1. karl_jones

    Jan 04, 2019

    Please file a new bug report If you are still encountering this problem. The error message is a symptom and can be caused by many different areas. The area for this bug has been fixed.

Comments (203)

  1. Askmejin

    Aug 13, 2017 16:19

    Happens always after a period of time (~half an hour) when switching from Visual Studio to Unity and hitting play. I have not experienced error to show up when using JetBrains Rider yet.

  2. GilesDMiddleton

    Aug 13, 2017 09:47

    Also just happened today with me - 2017.1.0f3 latest VSCode, mac. Had been working fine for hours, first time it's happened.

  3. madcowie

    Aug 12, 2017 00:50

    Happened to me twice today loosing 30 minutes of work each time. Only one instance of Unity Open and when I click Play :(

  4. matheustaveiros

    Aug 11, 2017 22:44

    Please fix this fast, crashes 3-7 times a day.

  5. Hermes_Zum

    Aug 11, 2017 19:25

    It happens sporadically in Unity 2017.1.0f3. I was left with the feeling that is caused in conjunction with VS 2017.

  6. johajo

    Aug 11, 2017 09:44

    Same issue for me. Happens irregularly, but typically each 2-4 hour into my work. No data is saved on crash. Typically happens when pressing play but cannot confirm that for every case.

    Unity version: 2017.1.0f3

    OS: Windows 10, 64-bit.

  7. tinkerer89

    Aug 11, 2017 02:28

    Unity 2017.1.0f3 running on Win7 Pro 64 bit version and the error pops up about every hour. It makes development a little more stressful wondering what I'm going to loose and when.

  8. Omniauric

    Aug 10, 2017 03:15

    2017.0.1f3 here. This is a brutal issue. Even though I'm paranoid and saving constantly, I'm still occasionally losing work. It's still early in this particular project, so I'm starting to consider maybe using a different engine.

  9. zenyata

    Aug 10, 2017 02:33

    it happens every 3-4hours.

  10. Hafazeh

    Aug 09, 2017 03:35

    This is happening here on my end as well, i might just have to go back to 5.6.0f3 as i was not getting this error there.

Add comment

Log in to post comment