Search Issue Tracker
Fixed in 2018.3
Fixed in 5.5, 5.6, 2017.1, 2017.2, 2018.1, 2018.2
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.
-
Olulekan01
Dec 24, 2019 20:06
I cannot believe I'm reading a wonderful presentation like this. You have really done a great job gathering this great and interesting experience. Thanks for sharing. For further experience:
https://www.happybirthdaysisters.com
https://developers.oxwall.com/user/Jojocote
https://twinoid.com/user/9900276
-
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
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
- Native object references for some object types are always 0 in the memory profiler
- Acute shadow acne when using two overlapping spotlights
- Raycast made on UI with multiple graphic Raycasters sort strangely when being on the same sorting layer and order
- Tabbed headers in editor windows need a style update
- [Android][IL2CPP] App crashes after executing Application.Quit
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.