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.
Comments (203)
-
ZenithSal
Jul 13, 2018 13:30
Issue just happened in 2018.2.0f2, so still here.
-
WheresMommy
Jul 12, 2018 17:31
2018.2 official release, still getting the error randomly
-
hippocoder
Jun 28, 2018 20:55
201.2.0b10 does it.
-
noorbeast
Jun 08, 2018 08:22
Definitely not fixed in 2018.2.0b7, as I just ha it happen.
-
sihame
Feb 05, 2018 14:43
Me too I still have it. I am on Unity 2017.1.0f3
-
NeoGeek
Jan 23, 2018 16:55
STILL getting it. Urgh
-
Barry100
Nov 01, 2017 11:10
im still getting this 2017 1.1.f1
-
vdarned
Oct 25, 2017 06:23
I got it guys I know when it happens: It happens every time unity become selfaware
-
karl_jones
Oct 17, 2017 10:44
@TNQIANG That callstack is not related to this issue. Please file a new bug so we can investigate.
@GWOLF Please use the patch, it is not fixed in that version. -
tnqiang
Oct 15, 2017 14:11
I use Unity 2017.1.2f1 and this still occurs.
My callstack is as following:0 il2cpp::vm::LivenessState::AddProcessObject(Il2CppObject*, il2cpp::vm::LivenessState*) (Liveness.cpp:334)
1 il2cpp::vm::Liveness::FromStatics(void*) (Liveness.cpp:203)
2 GarbageCollectSharedAssets (TimeHelper.h:26)
3 IntegrateMainThread (UnloadUnusedAssetsOperation.cpp:46)
4 UpdatePreloadingSingleStep (PreloadManager.cpp:478)
5 UpdatePreloading (PreloadManager.cpp:613)
6 PlayerLoop (PlayerLoop.cpp:104)
7 UnityPlayerLoopImpl (LibEntryPoint.mm:223)
8 UnityRepaint (UnityAppController+Rendering.mm:326)
9 -[UnityAppController(Rendering) repaintDisplayLink] (UnityAppController+Rendering.mm:78)
10 CA::Display::DisplayLinkItem::dispatch(unsigned long long) + 44
11 CA::Display::DisplayLink::dispatch_items(unsigned long long, unsigned long long, unsigned long long) + 436
12 IODispatchCalloutFromCFMessage + 360
13 ___CFMachPortPerform + 180
14 ___CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 56
15 ___CFRunLoopDoSource1 + 436
16 ___CFRunLoopRun + 1752
17 CFRunLoopRunSpecific + 420
18 GSEventRunModal + 96
19 UIApplicationMain + 196
20 main (main.mm:33)
21 _dyld_process_info_notify_release + 32
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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
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.