Search Issue Tracker

Fixed in 2018.3

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



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


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

  1. 6eaec9c6f56d1517958733fac1fabde3?d=mm


    Aug 19, 2017 20:46

    Zeday, this issue doesn't affect scripts. It affects the editor, not monodevelop or your other scripting programs, so just don't close out of your other programs. I hope this helps you moving forward if you ever experience this issue again.

  2. Dc1b254760f44d16cd4f684456bf554f?d=mm


    Aug 18, 2017 15:24

    A possible fix is on the way.
    Please direct feedback to this thread:

  3. Aff8fc7166d982bd670e1d90aab016ed?d=mm


    Aug 18, 2017 04:24

    I'm new to Unity so I thought that maybe this was a known issue with a workaround. I'm pleased to see that I'm not the only one with this issue but very annoyed like everyone else at the amount of work I've lost.

    Same thing for me: Occurs randomly after about 30 minutes to an hour. I've found that sometimes my work reverts to a state before my most recent save of the project which forces me to pray every time I reopen after a crash that my work didn't revert too far.

    Working with a MacBook Pro.

  4. E68f3fd980fe292e9ee28caebfc35969?d=mm


    Aug 17, 2017 02:05

    009, I started experiencing this error almost immediately upon installing 2017.1.0f3. I did not enable the Collaboration service and had it occur several times. So far, the "using Visual Studio as script editor and hitting the Play button" seems to be the most likely trigger in my case. But since it doesn't always happen right at the instance that I hit play or quit play, I can't be certain.

  5. 90af5cb444e49113735c00e690af5520?d=mm


    Aug 17, 2017 02:00

    Is it possible that is cause by Unity Collaborate ? Found out the only differences from me and my colleagues is this.

  6. 90af5cb444e49113735c00e690af5520?d=mm


    Aug 17, 2017 02:00

    Is it possible that is cause by Unity Collaborate ? Found out the only differences from me and my colleagues is this.

  7. 7acb3a48fc874dd4b32db9a644be779f?d=mm


    Aug 16, 2017 20:06

    Oh, Unity, WHY.....??? Why have you done this to me ...and others apparently??
    I have lost hours of work, hundreds of lines of code.

  8. 2bfd18e078ab086d8dda165caa3882ac?d=mm


    Aug 16, 2017 17:00

    Same problem... annoying as hell. I've lost so much work and finding I have to save every little change I make. Any update on when this will be fixed.

  9. 90af5cb444e49113735c00e690af5520?d=mm


    Aug 16, 2017 08:30

    Occur when after I edit the code with monoDevelope and come back to the Editor. about 5 times within 6 hours of working. Hope this can fixed soon.

    Unity 2017.1.0f3 in Window OS

  10. 04acf4ab7adba6df33a9bebb9e101413?d=mm


    Aug 16, 2017 03:46

    Happening to me since upgrading to 2017.1.0f3 . It's consistent after 30 minutes to an hour of use, it crashes. It usually seems to crash while I'm saving, but that's not always.

    OS: Mac

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.