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. 7acb3a48fc874dd4b32db9a644be779f?d=mm

    zeday

    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.
    WHY?????!

  2. 2bfd18e078ab086d8dda165caa3882ac?d=mm

    frankmat

    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.

  3. 90af5cb444e49113735c00e690af5520?d=mm

    009

    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

  4. 04acf4ab7adba6df33a9bebb9e101413?d=mm

    demonpants

    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

  5. B6ead0b30a2a3467d2c3b9f9e030c96e?d=mm

    rrahim

    Aug 15, 2017 14:36

    I've been having this issue since switching to 2017.1.0f3.
    It seems to be a random issue and causes alot of wasted time. Is there currently any workaround for it?

  6. F27617e362df1b431c68e2cbc49040bf?d=mm

    xtyler

    Aug 14, 2017 18:23

    Mac, 2017.0.1f3 - Please let me know if I can help repro, I get it several times a day and it's very hurtful to our progress.

  7. 854e499507e78aa82deb1c6a8858435c?d=mm

    screenname_taken

    Aug 13, 2017 22:11

    God! Please friggin fix it! We are losing progress and need to reset scenes!!!
    The hell?! 2017.1.0p3 and still happening.

  8. 40d9242731643561050862cdb8f66f2b?d=mm

    Lucid-Amusement

    Aug 13, 2017 17:11

    This is clearly happening to a large group of people and is certainly a hefty annoyance. Can we get some official Unity word on what the plan is for this? If this issue was any more frequent it would be a show stopper.

  9. Ea7a78df7acb9ead19af66d6199a1bbf?d=mm

    Askmejin

    Aug 13, 2017 16:19

    Happens always after a period of time (~half an hour) when switching from Visual Studio to Unity and hitting play. I have not experienced error to show up when using JetBrains Rider yet.

  10. D02f347f4985918306796bff3bb47ded?d=mm

    GilesDMiddleton

    Aug 13, 2017 09:47

    Also just happened today with me - 2017.1.0f3 latest VSCode, mac. Had been working fine for hours, first time it's happened.

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.