Search Issue Tracker
Fixed in 2018.3
Fixed in 5.5, 5.6, 2017.1, 2017.2, 2018.1, 2018.2
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.
-
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 -
gwolf
Oct 09, 2017 17:27
Definitely still a problem as of 2017.1.1f1, although it seems to be a more infrequent.
-
heliojmsemedo
Oct 04, 2017 12:04
Why is this not fixed 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
- Aplying changes to root prefab in a nested prefab undo changes made to the child prefab
- Sub Emitter particle's width is twice its height when Separate Axes in the Size over Lifetime module is enabled and set to 1
- Animation does not play correctly when Optimized Game Object functionality is used and a Child GameObject is added to bone
- An object created via "Create Empty Child" of Hierarchy panel in Prefab Mode is always a child of the main prefab
- [VCS] Version Control window could use a search field to filter down contents
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.