[Annoying bug] Editor crashing with "Increase kMaxCallback."

So guys. Are you gonna fix this or not?
Cause it's really frustrating to have the editor crash the moment you press play or simply give focus back to the editor and not be hitting CTRL-S like a mad man.
It's really infuriating. And yes, i have submitted a bug, 2-3 weeks ago.

 

The issue is listed as active - hoping for a fix soon too because it's painful crashing a dozen or more times a day.
https://issuetracker.unity3d.com/is...ror-callback-registration-failed-kmaxcallback

 

Yes, i was informed about it, but i was hoping such a bug would get a hotfix or make it into a patch.
It's easy to lose progress because of it.

 

Yeah happened to me twice today. Lost about 30 minutes work each time as Im not use to saving that often as Unity 5.4.1 was solid. Hope a fix comes soon.

 

I updated Unity a few weeks ago - at the current moment - i still regret it...

I get this crash like 6 times everyday, when pressing play or focusing back on editor.

When are we getting a fix? Hope it comes soon.

 

Am also regretting upgrading, this crash happens two or tree times a day, it just happened right row. . .on top of that the work offline button is giving me hell, It doesn't want to work without an internet connection. . .I expected a lot from unity 2017.1, they should have just called it unity 5.7

 

It's one thing to put new stuff in, but a whole different thing when you manage to brake important stuff that were working as they should in the magnificent way of "wham, you didn't need that progress, did you?"

 

I've had this issue a total of 6 times yesterday...

 

Hi Karl,
I've recently upgraded to 2017.1.0f3 from 5.6. I've never had the issue until upgrading to 2017.
The current project does not use collab.

I've had the issue up to 6 times on one day, and only once yesterday so it seems fairly random.
If it does happen today, I'll update you with my observations.
Thanks.

 

Using Unity 2017.1.0f3 OSX and Win 10 64bit (with VSCode on OSX and Visual Studio 2015 on Win). The kMax crash is happening on both versions about a dozen times a day and I'm not editing the same projects on both machines. Not using collab, not switching build targets. The Unity bug reporter does not automatically appear and I haven't seen any crash dumps or anything useful in the Editor.log.

It seems to happen randomly, sometimes occurring when returning from code editing and compiling, then playing, other times just when clicking play during normal editing.

 

Hi, well, i've had the issue since v2017, but the original bug says that is from earlier than that.
I am using collaborate and do use it quite a lot i think.
I'm also using VS community 2017 if that would make any difference.
I do think that it happens more often when i'm tweaking a scene and going in and out of Play mode.
But it also happens when i simply give focus to the editor. I may be in VS writing some code, or in a browser window checking things. And when i go back to the editor, it may just go puff!

 

I just had this crash 2 times for today. So far it's been after doing some scripting in VS community 2017, then switching back and upon pressing play.

Awesome, will test as soon as its available.

 

This happened to me once yesterday, lost 30 minutes of work. Happened to me again today and lost 3 hours of work. Thank goodness the scripts I was working on themselves saved, that was most of the headache I progressed through. This seems to happen when I click "Play" to see the effects real-time. This is a random bug which is very spontaneous and infuriating that needs to get fixed ASAP. The only protection is to save after every little change.

 

@karl_jones It just crashed, I didn't press play, i was going back and forth Editor <-> VS Community 2017 as i was making code changes and exposing public stuff, and hiding others with private.

 

Editor log looks normal. Couldn't find a crash log. Editor just goes away with after that message.

 

Seems fine. I've been inlining my own replacement of harsh language for it for a few weeks

(Just pm'd you a crash report and Editor log too. My original bug report was closed as a duplicate.)

 

Hows the fix going? This error has been happening to me all morning and it's frustrating as hell. What's going on?

 

64 isn't that many really. I'd expect thousands of those during a day.
Do you guys have suites of automated UI and unit tests for unity continually running? Seeing what tools/devops you guys use in development of unity It make for an interesting blog post.

 

Thank you.

 

just want to add to this, and say thank you for working on a fix, i wish i could send logs, but they seem to not be getting created when the crash happens for me. but as far as i can tell it's equal to what others are exp here. Make changes in VS 2017, return, and on pressing play.... death.... and lost work.

thank you!

 

That's great news

 

I'll be hitting that refresh button like crazy on Friday

 

This bug is reported to occur way back with Unity 5.5. I hope you will patch the non 2017 versions as well. The issuetracker bug itself reports found in 5.6.0b5.

 

Pardon, I couldn't say officially. I am basing it on comments found in the issue tracker thread.

---

Continuously happening to me on 5.5.0f3. I don't even have the program open for that long, sometimes <30 mins

This happened to me in version 5.5.2f1. Unity left open for at least a day or two without closing (computer on sleep overnight). Received this message after 8ish hours of use on the last day).

Just happened to me on 5.50f3 on Windows. Unity left open overnight, then crashed after 45mins of use. After updating a CS file in VSCode, crashed when returning to Unity.

 

*raises hand*
Is the K in kMaxCallback for Karl? I'm not trolling, I'm genuinely asking.

 

It's (usually) a programming convention that specifies that variable as a constant.

 

Dang it. It would be awesome
I'm usually appending const to a variable.

 

The fix for this is not in today's patch, is it?
Can't find any mention of bug case 873467.

 

The 2017.1.0.p5 actually broke the lighting in the editor window in linear mode. for me anyway

 

I did, i did. i hope more people have as well as i'm not the only one with the issue it seems.
It's case number is #945391
https://forum.unity3d.com/threads/bug-unity-2017-1-0-p5-everything-went-dark.490458/

 

To get a patch do I have to download a whole new editor or is it a small download?

 

It's a whole install. The updates are not incremental as to make sure that everything needed is downloaded.
https://unity3d.com/unity/qa/patch-releases
So basically you can download a patch release without having any previous install.
The difference is that the "full" or "final" release is supposed to be tested and true that works as it should. (never mind the bugs that the patches are supposed to fix )

 

It's insane how much work I lost in the last week due to this bug. Can't wait for the patch.

 

I just came here after getting this error too, looking for news of a fix.

Glad to see it's being worked on, thankfully I don't lose work when it happens.

 

I wish i'd seen that before downloading gigabytes lol.
At least I can confirm the bug is still present in the p5

 

Hey guys, so is the fix in 2017.1.0p5? didn't see it in the notes.


EDIT: aw crap just saw the comment above!

 

Guys, what about beta 2017.2.0b9? Didn't anyone test it?
I'm downloading it now. I'm getting it it every 30/45 minutes on 2017.1.0f3.

 

The fix is coming tomorrow as far as i know.