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

It's happening to me a lot and I'm not using collab.

Thanks for the attention and the work Karl , friday it's going to be a happy day

 

Waiting with baited breath

 

Tomorrow, maybe? Nice. I'll be glued to patch page haha.

 

According to the post in announcements this patch isn't due until 6th-8th Sept

 

Aw that's a shame...

But it's still not that far off!

 

I can't wait till this is fixed this happens to me a lot. Luckily I save after pretty much everything I do, but it sucks being completely in to a project and then bam time to reopen unity. Makes me lose momentum Haha.

 

Yeah, totally! I've put off the coding process till it's fixed. Thankfully I have a lot to keep me busy, especially asset importing!

 

Is this the bug support group? My name is George. The damn thing crashed while compiling.

 

While compiling? Geez, that musta damaged some data. :/

 

Oddly enough, the scene in the editor seems fine.
I'm guessing it i'll show up later one when i go and use a plugin or something

 

Thank the lord

Downloading now, I'll give it a go and see if it's fixed the crashing.

 

It also fixed the dark editor in linear mode!

 

Sadly still getting crashing, although not with the kMaxCallback message (which I only used to get about once every three crashes). Sometimes it brings up the bug reporter, sometimes it just freezes and eventually closes.

Maybe there's something else going on here, but I didn't encounter the regular crashes prior to upgrading to Unity 2017.

 

Thanks - 2017.1.1p1 just delivered my first day without any kMaxCallback crashes since 2017.1 was released.

 

I upgraded to Unity 2017.1.1f1 the other day and I still gets this annoying error message with the crash. Wasn't this supposed to be fixed?

 

It is, but not in f1. It's fixed in p1, you need to download the latest patch.

 

The crash only happens approx. every 10 - 15 times I run the program (or switch back to Unity after editing scripts), sometimes as soon as I press play, and sometimes a few seconds later, and I can only reproduce it with my complete project, which is quite big (the project folder is around 1.5gb in size).

The problem doesn't seem to affect the built program, as I have successfully run multiple instances on the same PC constantly for a number of hours whilst testing network performance, with none of them crashing once.

Is this something you'd be able to look at or do you think there will be too many variables involved, because off the size of the project?

 

I've submitted a bug report, Case 950161

Thanks

 

Also happened to me first time today in 2017.1.1f1, here is a screenshot but it did not show the bug screen

 

Hi all,
I didn't download the 2017.1.1p1 version yet, but I will tomorrow, but I have 2 questions first.

The update check screen appeared and notified me that there is anew version (2017.1.1f1).
But, since the "good" version is 2017.1.1p1... Here is my question:

Do I need to download 2017.1.1f1 and then apply the patch from Karl's link?
Or the installer from http://unity3d.com/unity/qa/patch-releases is enough and also includes the last version (like a full download)?

In case I need to download 2017.1.1f1 and then apply patch, if I want to install the recent patch (p2), do I need to install p1 first?


Sorry if it's a noob question. I mean, I've never applied a patch to Unity, I've always downloaded as a full installation.
The download page https://store.unity.com/es/download?ref=personal says Versión 2017.1.1, but I don't know if it includes p1.

Thank you so much

 

Oh, great. Thanks

 

A few days working with 2017.1.1p2 and the error seems that has gone (touch wood)
So thanks

 

damn bug, It f**** me so hard, anything was gone !!!!

 

It looks like the other crashes I was getting may have been related to a crash when using Linq, which was fixed in Version 2017.1.1f1

 

That fixes the kmaxcallbacks crash but I still get editor only crashes even with 2017.1.1p1.

I hadn't realised p2 and p3 had been released. Does p3 contain the fixes that are in p1 and p2?

also does p3 contain all the fixes that are in 2017.1.1f1?

 

Hi Karl,

thanks for the response, yes I am referring to the crash I reported in #950161.

For some reason I didn't see the response on 20th September. I am indeed using the experimental 4.6 version of .NET; I had switched to that to test it, and I thought I'd reverted back, but I must have forgotten.

I suspect that may well be the reason behind the continued issues, so I'll switch back to the stable 'NET version and report back here after I've tested it again.

Thanks

 

No crashes so far today, so it looks like that was the reason.

Thanks for all the help

 

https://issuetracker.unity3d.com/is...istration-failed-kmaxcallback?page=1#comments

 

The bug persists even in 2018.2.2f1.