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.
-
TiagoSerra
Aug 04, 2017 03:16
Same here on both clean install of OSX Sierra latest update and also latest 64 bit windows 10
-
gss214
Aug 04, 2017 00:02
same here. win10 64bits and unity 2017.1.0f3
-
DavidErosa
Aug 03, 2017 15:12
Same with Windows 10 64 bita and Unity 2017.1.0f3. Editor closes and no bug report dialog. I can't find a way to reproduce it but for me it's always when I enter Play mode after coming back from Visual Studio.
-
VishalFbs
Aug 03, 2017 11:55
Facing same issue for window 8 and unity 2017.1.0f
-
Ashwin-Star
Aug 02, 2017 19:26
Fatal Error! > Callback registration failed. Increase kMaxCallback.
-
Ashwin-Star
Aug 02, 2017 19:24
happened twice so far, once when Played the scene another when switched from Mono to Unity. ver 2017.1.0f3
-
zapposh
Aug 01, 2017 10:41
Also happens in 2017.1 p2
-
bc-maia
Jul 30, 2017 02:35
well, it started here. In my case it happens when I left the editor idle for some time while working on Visual Studio, then when I return to the editor screen it dies.
:( -
Mr-Knieves
Jul 30, 2017 02:02
2017.1.0f3 MacOS Sierra.
-
Mr-Knieves
Jul 30, 2017 02:00
Keeps happening to me randomly. Not sure what is triggering it.
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
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.