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.
-
DefinitelyNotSteffen
Feb 21, 2020 09:10
I Still get this error in 2018.2.21f1.
-
ellend
Apr 30, 2019 08:22
Happened to me many times，v2018.2.3f1
-
Ruufer
Apr 23, 2019 01:01
STILL HAPPENING IN 2018.2.0f2
-
nuToH
Sep 13, 2018 13:58
2018.2.7 Not fixed. What to do? Wait for 2018.3?
-
reuno
Sep 02, 2018 18:11
This is becoming annoying.
Happens on a daily basis now, and has for a month or so (using 2018.2.x.
I never encountered it before 2018.2 (or so rarely I never noticed it). -
stormred1236
Aug 31, 2018 22:30
Still the case for me too....
-
Baraff
Aug 30, 2018 05:09
Related but unrelated. I get this same crash message in the log in windows standalone build when I run the build when built with 2018.2.5f1 but it works fine when built with 2018.2.3f1
Callback registration failed. Increase kMaxCallback.
(Filename: Line: 191) -
MVRKHQ
Aug 29, 2018 19:47
it's still happening regularly on 2018.2.0f2
-
zornor90
Aug 29, 2018 00:39
Still happening on a build with Unity 2018.2.5 - NOT fixed
-
royrextred
Aug 26, 2018 14:38
Still not fixed
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
- Light brightness gets intense until the 'Lightmap Encoding' quality is changed when baking Lightmap
- Crash on LinearCollectionField::LinearCollectionField after a 'm_ArrayField != SCRIPTING_NULL' assertion when opening a project
- Import Activity Window takes long time to open
- [Android] Artifacts appear in texture Preview Window on Android Platform when selected Override ETC2 fallback is 16-bit
- Child Canvas' Sorting Layer is changed to the same value as the parent Canvas after interacting with Dropdown UI object
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.