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



Found in



Issue ID




Unity throws out Fatal Error: Callback registration failed kMaxCallback



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

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

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

  1. GameEverything

    Sep 18, 2017 22:19

    Lol, what are you talking about? This issue isn't fixed and I'm using version 2017.1.0f3. In fact, this time around it actually corrupted my project where now the project won't even load causing a crash each time.

    Oh, I do want to say, though, that I appreciate all of the hard word you put into fixing these issues and I know I sound a bit snarky, lol. :)

  2. Dawid_Matuszewski

    Sep 18, 2017 12:13

    The same here
    System: Windows 10 Pro 64 bit
    Unity : 2017.1.1f1 64 bit
    it's very annoying - every ~30 minutes.

  3. EliasHasle

    Sep 17, 2017 19:31

    Same problem in version 2017.1.1f1 education version on Windows 10 x64. Running the update tool from the help menu says this is the most current version.

  4. unigeek

    Sep 16, 2017 19:54

    The issue remains in 2017.1.1f1

  5. karl_jones

    Sep 13, 2017 11:35

    If you still have this issue in 2017.1.1p1 then please file a bug report and/or post here with your log file

  6. Lukas-Wendt

    Sep 12, 2017 11:53

    Still an issue on 2017.1.1f1

  7. krisbeck

    Sep 12, 2017 11:21

    At least do the auto save on forced exit!

  8. jinnindo

    Sep 12, 2017 03:27

    This is *not fixed in 2017.1p1

    You're giving me trust issues, unity.

  9. Warsymphony

    Sep 12, 2017 00:48

    Still getting this error 9-11-17

  10. godboldADX

    Sep 11, 2017 18:53

    Getting this issue with Unity 2017.1.0f3

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.