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.

Comments (203)

  1. Mighto360

    Aug 08, 2017 13:56

    Happens on macOS Sierra 10.12.5, Unity 2017.1.0f3. It's a big problem for me.

  2. BoraxKid

    Aug 07, 2017 11:25

    Happens here on Unity 2017.1.0f3 on Windows 8 Entreprise 64 bits.

    The Bug Report window did not show up

  3. hht

    Aug 07, 2017 08:38

    Happens very often in Unity 2017.1.0f3 on macOS Sierra 10.12.6

  4. Cemaprjl

    Aug 07, 2017 03:51

    windows 10, 2017.1.0p1, comes several times in a day

  5. Denki_Gaka

    Aug 05, 2017 01:24

    Occurring multiple times each day in 2017.1.0f3. Never saw before that. However, I am getting much better about saving my scene every time before I run. 8^)

  6. BoaNeo

    Aug 05, 2017 00:44

    Oops, forgot the details: 2017.1.0f3 running on OsX, latest mac book pro... Seem to happen regardless of size and nature of the project I have loaded, and so far it has always happened when pressing play (I only have one instance running).

  7. BoaNeo

    Aug 05, 2017 00:36

    Also seeing this every odd-hour randomly after upgrading to 2017.1

  8. archelyte_vz

    Aug 04, 2017 18:32

    This is happening about 3-4 times a day. This is ridiculous.
    2017.0.1f3

  9. RFJ

    Aug 04, 2017 07:48

    Yeah BIG problem for me and my team happens at least 3 times a day

  10. Zakari

    Aug 04, 2017 03:43

    ye, this is a big problem for me.

Add comment

Log in to post comment