Entering "Deep Profile" crashes the editor 100% of the time.

This bug is marked as fixed but its happening to us again. Clicking “Deep Profile” soft locks unity for about 10 seconds without displaying the “Unity thinking wheel”. Then when you enter play crash.

Its from 2015 was 100% repro then and still seams to be for some people. It came out of no where though ( I was deep profiling fine before) maybe another library issue? Also we have auto-refresh disabled as with large projects it causes unity to hang way too much when working between code and editor to be useable. Disabling auto refresh causes a ton of new crashes though (but we are needing to pick crashes over a complete inability to get things done) Maybe this is related to auto-refresh?

Also as a note, turning deep profile on then off before entering play does not cause the crash. Turning it back on does though.
Thanks.

Happens to me also. Was working fine, then one day it just crashes after a second when running a scene. It always crashes on that scene (a very complex one) but I’ve tried it on a empty scene and it works there.

I get the debug the crash dialog from windows, where I can see exception thrown is AccessViolation from KernelBase.dll.

This is from editor log:
RtlLookupFunctionEntry returned NULL function. Aborting stack walk.
0x00007FF8E02A7788 (KERNELBASE) RaiseException
0x00007FF8A5541158 (mono) [c:\buildslave\mono\build\eglib\src\goutput.c:201] g_logv
0x00007FF8A554117C (mono) [c:\buildslave\mono\build\eglib\src\goutput.c:211] g_log
0x00007FF8A5662F14 (mono) [c:\buildslave\mono\build\mono\mini\mini.c:3196] mono_codegen
0x00007FF8A5663E78 (mono) [c:\buildslave\mono\build\mono\mini\mini.c:4016] mini_method_compile
0x00007FF8A56647FB (mono) [c:\buildslave\mono\build\mono\mini\mini.c:4344] mono_jit_compile_method_inner
0x00007FF8A5664E19 (mono) [c:\buildslave\mono\build\mono\mini\mini.c:4556] mono_jit_compile_method_with_opt
0x00007FF8A5664EAC (mono) [c:\buildslave\mono\build\mono\mini\mini.c:4580] mono_jit_compile_method
0x00007FF8A565CF83 (mono) [c:\buildslave\mono\build\mono\mini\mini-trampolines.c:477] mono_magic_trampoline

1 Like

Same here:

KernelBase.dll!RaiseException() Unknown
mono.dll!g_logv(const char * log_domain, GLogLevelFlags log_level, const char * format, char * args) Line 201 C
mono.dll!g_log(const char * log_domain, GLogLevelFlags log_level, const char * format, …) Line 211 C
mono.dll!mono_codegen(MonoCompile * cfg) Line 3196 C
mono.dll!mini_method_compile(_MonoMethod * method, unsigned int opts, _MonoDomain * domain, int run_cctors, int compile_aot, int parts) Line 4016 C
mono.dll!mono_jit_compile_method_inner(_MonoMethod * method, _MonoDomain * target_domain, int opt, _MonoException * * jit_ex) Line 4344 C
mono.dll!mono_jit_compile_method_with_opt(_MonoMethod * method, unsigned int opt, _MonoException * * ex) Line 4556 C
mono.dll!mono_jit_compile_method(_MonoMethod * method) Line 4580 C
mono.dll!mono_magic_trampoline(__int64 * regs, unsigned char * code, void * arg, unsigned char * tramp) Line 477 C

1 Like

I think I saw this mentioned as a problem they fixed in one of their recent 5.5.2 patch releases

I found crash source for me, it’s cause by GridLayoutGroup. If i disable this component in my opened scene, Deep Profile stop crashing!

Same here with 5.6f

Same here with 5.6f

Same here with 5.6f

1 Like

Same here in 5.6.0f3 - 100% crash when clicking Deep Profile. Can confirm that disabling all GridLayoutGroup objects “fixes” the crash.

1 Like

For the GridLayoutGroup crash, I have received a message from a Unity developer: “should be fixed in next patch releases”

2 Likes

No more crash when pressing “Deep Profile” with Unity 5.6.1f1. Thanks to developers.

1 Like

Still broken for me on 5.6.1f1.

Same here on 5.6.1f1, and when I try to submit a crash report the dialog just sits there with “Packing the report…” at 0% and never submits.

[edit: I figured out it wasn’t submitting because my project was being attached to the report by default, and it’s too big to upload]

I think I have found a work around for this. If you start deep profiling in a simple scene (In my case a menu scene) and then use that scene to load the one you want to profile then it prevents the crash

Same issue with 2017.1.0f3, but it’s not always happening but currently like 70% of all tries.

PS: Not aware of any GridLayoutGroups in our project (at least neither from code nor in the scene).

Still happening with 2017.2.0f3, Have not been able to debug this is caused by GridLayoutGroup.

Still happening with 2018.1.6f1

Please file a bug.
Also try to use the new scripting runtime to see if it makes any difference.

I am using .Net 4.0 Equivalent but still facing the same problem in 2018.2
PS: macOS 10.12