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
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.
-
sbrodie
Jul 14, 2017 17:59
Happening regularly on Unity 2017.1.0f3, both new and upgraded projects.
-
darthbator
Jul 14, 2017 08:47
This issue is not fixed I am still encountering it as well
-
Cynikal
Jul 14, 2017 06:30
Just happened to be in the latest release of 2017.1.0f3
-
ventedpennies
Jul 14, 2017 04:22
This is not fixed for 2017. I have never received this error, now I receive it on a regular basis.
-
RafayAli
Jul 13, 2017 12:12
Its happening ever since I installed 2017.1, never happened even once when using previous versions.
-
ReneBuehling
Jul 12, 2017 17:27
This is NOT resolved. It still happens in 2017.1.0f3 (64-bit)
Actually it happens even *since* I am using 2017.1, and did not happen before. :(
-
Atticite
Jul 11, 2017 19:38
Just encountered this one in 2017.1.0f3, so not entirely fixed ...
-
fogsight
Jul 02, 2017 01:27
"Fatal Error!
Callback registration failed. Increase kMaxCallback."
Unity 2017.1.0f1
Happens sporadically. Last time on Alt-Tab back when left running scene in Play mode. -
Lepascal
Jun 20, 2017 10:38
Idem in Mac Unity 2017.1.0.B9.
-
himzy
Jun 18, 2017 14:54
Still happening
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
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.