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.
-
maxsun
Jul 29, 2017 23:38
same win10 2017 f3
-
JannickL
Jul 29, 2017 22:16
Same for me. Win 10 and Unity 2017.1.0f3.
-
iDeveloper2
Jul 29, 2017 12:50
I also facing this issue in unity 2017.1.0f3
-
Johngun
Jul 29, 2017 11:27
Same here, plus all work is lost, macOS 10.12.5, unity 2017.1.0f3
-
Gri94
Jul 28, 2017 14:29
Same problem, Windows 10, unity 2017.1.0f3
-
polycube
Jul 28, 2017 00:46
I have same problem. It happens almost every two hours...........
-
sevensails
Jul 27, 2017 19:09
I have the exact same problem!
-
NRF
Jul 27, 2017 14:08
Same problem here (Unity 2017.1.0f3, Win10 [resettet my OS 2 weeks ago from win8 to win10]).
Last 15 times it happens after changing some .cs when pressing the Play button (between 3h and 30min). But 1 time (last one) it happend after i drag and dropped a prefab from an other project to my project, then i grabbed the prefab in Unity and wanted to drag and drop it into the hierachy, but after dragging it it crashed. -
Laniemme
Jul 26, 2017 23:40
I keep getting this occasionally too. I will press play, the dialog box appears, I click Quit and...well you can guess what happens next. Windows 10, Unity 2017.1.0f3. I'm glad I have an autosave asset so I don't lose any work.
-
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.
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.