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.
-
009
Aug 17, 2017 02:00
Is it possible that is cause by Unity Collaborate ? Found out the only differences from me and my colleagues is this.
-
zeday
Aug 16, 2017 20:06
Oh, Unity, WHY.....??? Why have you done this to me ...and others apparently??
I have lost hours of work, hundreds of lines of code.
WHY?????! -
frankmat
Aug 16, 2017 17:00
Same problem... annoying as hell. I've lost so much work and finding I have to save every little change I make. Any update on when this will be fixed.
-
009
Aug 16, 2017 08:30
Occur when after I edit the code with monoDevelope and come back to the Editor. about 5 times within 6 hours of working. Hope this can fixed soon.
Unity 2017.1.0f3 in Window OS
-
demonpants
Aug 16, 2017 03:46
Happening to me since upgrading to 2017.1.0f3 . It's consistent after 30 minutes to an hour of use, it crashes. It usually seems to crash while I'm saving, but that's not always.
OS: Mac
-
rrahim
Aug 15, 2017 14:36
I've been having this issue since switching to 2017.1.0f3.
It seems to be a random issue and causes alot of wasted time. Is there currently any workaround for it? -
xtyler
Aug 14, 2017 18:23
Mac, 2017.0.1f3 - Please let me know if I can help repro, I get it several times a day and it's very hurtful to our progress.
-
screenname_taken
Aug 13, 2017 22:11
God! Please friggin fix it! We are losing progress and need to reset scenes!!!
The hell?! 2017.1.0p3 and still happening. -
PNUMIA-Rob
Aug 13, 2017 17:11
This is clearly happening to a large group of people and is certainly a hefty annoyance. Can we get some official Unity word on what the plan is for this? If this issue was any more frequent it would be a show stopper.
-
Askmejin
Aug 13, 2017 16:19
Happens always after a period of time (~half an hour) when switching from Visual Studio to Unity and hitting play. I have not experienced error to show up when using JetBrains Rider yet.
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
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.