Search Issue Tracker

Fixed in 2018.3

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

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. Response avatar

    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 (201)

  1. E244ded82bac2850103e02688299c26c?d=mm

    jet-pack

    Aug 07, 2018 12:36

    Happens to me every 4-8 hours. 2018.2.0f2, Windows 10.

  2. Fa58be433541aee22c0da27c7fe1bf62?d=mm

    Canabinoide-Games

    Aug 05, 2018 18:00

    still happens to me on 2018.2.2f1
    approximately 1 out of 10 times i click on play to test my game, the crash comes.

  3. A3a43487ce4126a5c71e6126f32d5e71?d=mm

    hippocoder

    Aug 04, 2018 12:17

    "Fixed in future release" but it would be really nice to know what fixes it. This is so if we get a bug in future, we can at least immediately test that case as well, to better create repro cases.

  4. E634896fa2c9b9dfdcbe6a5bbff82573?d=mm

    Eldrix

    Aug 04, 2018 02:52

    Happened today in Unity 2018.2.2f1 after working in Unity for a couple hours. I luckily just saved my project.

  5. A66b6a6d70300b827a384ebbd01322f3?d=mm

    Linkupdated

    Aug 04, 2018 01:15

    Still happens in unity 2018.2.0f2

  6. Cf237c88dcf023c16ea55751472c9194?d=mm

    Broendholt

    Aug 02, 2018 21:33

    After setting to Colors (Color) as public variables and saving the script (MonoBehaviour) The fatal error happened.
    Unity had been open for around 5 hours.

  7. Ef2a456b85f27a41cf53ef34115e89f4?d=mm

    dccatalin

    Aug 02, 2018 19:26

    Happens to me in 2018.2.0f2 (Windows), usually when recompiling scripts after editing in Visual Studio. Using latest Unity extensions for Visual Studio.

  8. 4c2ca67127844ff986042e09ba4ba83e?d=mm

    DeadHandInteractive

    Aug 02, 2018 19:07

    Happened to me when editing cloth weights in Cloth component

  9. Abcf84d9d9261efed6f6cfe09c7e7b3a?d=mm

    MVRKHQ

    Aug 02, 2018 18:15

    happens to me on 2018.2.0f2

  10. D1046e176e3436515b7339184e32a0c9?d=mm

    zero_null

    Aug 02, 2018 15:26

    happening to me as well. Just like GIAWA said, it randomly crashes when coming back from editing scripts in the visual studio most of the time.

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.