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)
-
Racsoth
Jul 26, 2017 19:38
+1 on this. Version: 2017.1.0f3. Has happened several times to me, randomly after pressing the Play button. Bug reporting window doesn't appear.
-
ArtyIF
Jul 26, 2017 19:29
same error when entering play mode when you did it like 5-6 times. 2017.1.0f3, windows 10. freaks me out every time it happens
-
Hadrien
Jul 26, 2017 13:33
Same problem here, this bug came out for the first time after I have update Unity from Unity5.6.2 to Unity 2017.1.0f3 personal.
It crash randomly, sometimes I can work for 3 hours without crash and sometimes for 30 minutes. -
Sudarmin-Then
Jul 26, 2017 12:20
Yes, still happening in Unity 2017.1.0f3, I'm using Windows 10, happens everyday but very random, usually after updating a .cs file and then going back to Unity Editor, sometimes it happened when I just kept open the editor for a few hours while I'm doing something else on the computer, when I came back to the editor it will crash with "Callback registration failed kMaxCallback"
-
FirstLightStudios
Jul 26, 2017 02:00
Unity 2017.1.0f3 Personal - PC Windows 10 Home - Happening fairly frequently
-
yigitdream
Jul 25, 2017 19:55
After the OS X 10.12.6 update all the versions give an error when unity unfocused in play mode. (5.6.1.p1 ,5.6.2p4 ,2017.1.0p1 )
-
mrm83
Jul 25, 2017 15:11
Mac OSX, Unity 2017 1.01f3, crashes every 30 mins.
-
Feelnside
Jul 25, 2017 14:27
The same issue for me was faced in Unity 2017.1.0f3 on Mac OS 10.12.6. Previously it was worked perfectly in Unity 5.6. It's very bad stuff and as far as I can see it's often reproducible after clicking the "Play" button in editor. You just trying to check some changes and the issue appears. As result all changed data is missed...
-
zzgrzyt
Jul 25, 2017 11:02
Crash log from 2017.1.0f3 when this error happened but the popup did not even show up and Unity just crashed: https://pastebin.com/Ciy211sy
It happened after I moved two scripts between folders in the Project window in Unity.
-
hwizard
Jul 25, 2017 07:39
2017.1.0f3 personal :( frustrating
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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element 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.