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.
Comments (203)
-
codingcat1
Mar 31, 2017 00:10
This happened to me in version 5.5.2f1. Unity left open for at least a day or two without closing (computer on sleep overnight). Received this message after 8ish hours of use on the last day).
-
davidhallahan
Mar 10, 2017 14:27
Just happened to me on 5.50f3 on Windows. Unity left open overnight, then crashed after 45mins of use. After updating a CS file in VSCode, crashed when returning to Unity.
-
LucVdB
Feb 06, 2017 10:18
Still happens in 5.6.0b5
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
- Performance drops significantly when many Tilemap modifications are made
- Help icons in the "Multiplayer Tools" window are poorly visible in the dark Unity theme
- Shadows are not present when using unity_SpriteColor and Alpha Clipping in Shader Graph
- [macOS] Secondary display rendering incorrect target and flickering when building for Multi-Display
- "Create Empty Child" Option Creates Root Object When No Parent Is Selected
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.