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.
-
himzy
Jun 18, 2017 14:54
Still happening
-
Barries19
Jun 01, 2017 00:35
Happened to me in 2017.1.0b7
Second time it happened, don't know the reason for it. -
nuthman
May 22, 2017 20:19
Just happened to me: 2017.1.0b5
-
FlopCoat
May 19, 2017 10:07
Still around in 2017.1.0b5
-
tdvance
May 12, 2017 15:52
Wait, why is this marked resolved? it clearly isn't....
-
tdvance
May 12, 2017 15:52
Happens in Unity 2017.1.0b4 almost every session.
-
haskins
May 01, 2017 22:48
It's happened a few times to me using Unity 2017.1.0b2.
-
SpookyCat
Apr 26, 2017 14:37
Still happens in Unity 2017b1
-
GameEverything
Apr 23, 2017 10:43
Occurs in 5.6.0b3. I'm just glad that it saves or whatever because I know I sure as hell forgot to save after five hours of work, lol.
-
swerly
Apr 04, 2017 18:48
Continuously happening to me on 5.5.0f3. I don't even have the program open for that long, sometimes <30min
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
- Scene is not rendered and appears black when the Custom Renderer Feature is utilized
- The Context Menu is not updated in the Shortcuts menu when resolving a Binding Conflict
- [Quest] Foveation Level is 0 when SRP Foveation is enabled
- Freeze when displaying text with "-T" in Play mode
- A particle is not rendered for the first frame when the duration and lifetime values match
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.