Unity Issue Tracker - Unity throws out Fatal Error: Callback registration failed kMaxCallback

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

Themes

Jan 23, 2017

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.

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.

Comments (205)

amisner2k

Jul 14, 2018 07:53

This also just happened for me on 2018.2.0f2
AA-Matt

Jul 14, 2018 07:35

Also just got this on 2018.2.0f2
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