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. AntiSilence

    Jul 19, 2017 00:03

    Had this happen in 2017.1.0f3 a few times now, didn't get it before updating. Windows 10.

  2. Tkrain42

    Jul 18, 2017 05:10

    Just happened to me on Unity 2017.1.0f3... It never happened on 5.6x, so I was completely and utterly unaware of it, and just lost a night's work....

  3. otyx

    Jul 17, 2017 15:40

    +1 from me too. Unity 2017.1.0f3 Personal on Mac.

    Good luck with the bug hunt!

  4. LordOfAzure

    Jul 17, 2017 00:17

    I've had this a few times now since upgrading to 2017 f3. I had never seen it before (I was using the most recent 5.6). Seeing as how unsaved work gets lost, it's become somewhat annoying... I have not yet observed a pattern to the cause.

  5. bberrevoets

    Jul 16, 2017 09:27

    I get this error about working every hour since I am using version 2017.1.0f3

  6. AndreM1

    Jul 15, 2017 20:05

    I sended them this bug reported when this one was marked as fixed:

    "Yep, again, this bug was present on 5.x, and it was said that was fixed, but it's not. I know, there IS another report of this exact same bug, but it's marked as FIXED, wich is absolutely not. That's a bug in the editor itself, and it's not related with the project because it happens with me independently of the project i work on, and with other people too. In previous versions it could even trigger an BSOD in Windows, wich doesn't happen anymore. It does not happen always, but it happens sometimes when switching tabs while the game is been played in the editor. In this version, the bug reporter doesn't oppen automactly, and in previous versions, unity showed an whole log of the error, in this version it just show "Fatal Error! Callback registration failed. Increase kMaxCallback.". It seems to be hapening more frequently than before. Please fix that, when it crashes, all the work made with the project except for the assets are gone. It's a huge pain."

    Then they replied with that:

    My name is Denisas and I have been investigating this case.

    We are having a hard time with this bug. As it seems like it happens totally random. We have not received any reports with f1, f2 or f3, so we assumed that it has been somehow fixed.
    I will reopen the 873467 case and forward it to the responsible person.
    Issue tracker link:

    Best regards,
    Denisas Kirilovas
    Unity QA team"

  7. NickerSq

    Jul 15, 2017 18:07

    I get this error every 1-2 hour, super annoying.

  8. dasoftca

    Jul 15, 2017 16:47

    Happening to me every hour or so with 2017.1.0f3. Never happened to me before 2017.1.0f3.

  9. Manumoi

    Jul 15, 2017 00:56

    Also happened to me just now. Windows 10, Unity2017.1.0f3

  10. ctronc

    Jul 14, 2017 20:57

    Has happened to me 3 times today. On Unity 2017.1.0f3. I'm doing some heavy alt-tabbing, maybe it's that?

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.