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.

Log in to vote on this issue

Comments (202)

  1. WobblyRampack

    Aug 26, 2017 23:20

    A dozen crashes a day with this error on MacOS with latest version of Unity. Praying for a fix.

  2. Barry100

    Aug 25, 2017 08:58

    this is happening to me now around 5 times per day! Very frustrating. Lost some work a few times now.

    2017.1.0.f3

  3. HiLiX

    Aug 23, 2017 10:25

    Most annoying bug! I almost destroyed my keyboard because of that ;) ... Still happening on Unity 2017.1.0p4(p3)

  4. Regnian

    Aug 20, 2017 18:51

    Ouch, save often and always before play mode! My scripts were not erased, but my editor creations were. Sadness is overwhelming. =P

  5. Blazerker

    Aug 20, 2017 13:22

    Please, please release an urgent fix for this bug! I get this up to 10 times a day working on projects! Occurs mostly switching between monoDevelop and Unity Editor often during debug sessions.

  6. piratepoots

    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.

  7. karl_jones

    Aug 18, 2017 15:24

    A possible fix is on the way.
    Please direct feedback to this thread: https://forum.unity3d.com/threads/annoying-bug-editor-crashing-with-increase-kmaxcallback.487655/

  8. numbus

    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.

  9. koikodo

    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.

  10. 009

    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.

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.

Latest issues

See all new issues