Crash almost every time when entering playmode

I just updated to Beta 4, and my project crashes almost every time I enter play mode, even in a new scene with nothing but a camera and light. The editor.log in the crash report just shows an access violation at address 0xfffffffff. Is there any way I can get more info on what might be causing the crash? New projects don’t seem to have this problem, so it must be something in my project causing it.

Any chance you can show us the stacktrace?

Same for me. I get constant crashes that I did not get with b3. I switched back to b3 now as b4 is unfortunately unusable in this state. I sent several bug reports so that you can follow up! I think I have 4 independent crashes reported now (3 in b3, all still there in b4 + this new one now) that all happen under different but reproducible circumstances which are all blockers for me.

I can give you access to my project (20gb Git) which should allow you to reproduce every single bug.

Bugs: 715050, 715048, 715005, 714983, 713630, 713395, 713310 (these are the crash bugs only :wink: I got major other ones reported as well that are also easy to reproduce)

>    Unity.exe!UnityScene::RemoveVisibleRoot(class std::_List_iterator<class std::_List_val<class Transform *,class std::allocator<class Transform *> > >,bool)    Unknown
    Unity.exe!Transform::MainThreadCleanup(void)    Unknown
    Unity.exe!delete_object_internal_step1(class Object *)    Unknown
    Unity.exe!CommitBatchDelete(struct BatchDelete &)    Unknown
    Unity.exe!DestroyGameObjectHierarchy(class Unity::GameObject &)    Unknown
    Unity.exe!DestroyObjectHighLevel(class Object *,bool)    Unknown
    Unity.exe!DestroyWorldObjects(struct dynamic_array<int,4> const &)    Unknown
    Unity.exe!Application::LoadSceneInternal(class std::basic_string<char,struct std::char_traits<char>,class stl_allocator<char,59,16> > const &,enum TransferInstructionFlags,class std::map<__int64,int,struct std::less<__int64>,class std::allocator<struct std::pair<__int64 const ,int> > > *)    Unknown
    Unity.exe!Application::EnterPlayMode(bool)    Unknown
    Unity.exe!Application::SetIsPlaying(bool)    Unknown
    Unity.exe!Application::TickTimer(void)    Unknown
    Unity.exe!RelaunchUnity(class std::vector<class std::basic_string<char,struct std::char_traits<char>,class stl_allocator<char,59,16> >,class std::allocator<class std::basic_string<char,struct std::char_traits<char>,class stl_allocator<char,59,16> > > > &)    Unknown
    Unity.exe!WinMain()    Unknown
    Unity.exe!strerror_s()    Unknown
    kernel32.dll!BaseThreadInitThunk()    Unknown
    ntdll.dll!RtlUserThreadStart()    Unknown

I did submit a bug with an attached crash dump as well.

Thanks.

We now have a clear way of reproducing this crash and we will get a fix it as soon as possible.

1 Like

Just wondering was this fix supposed to be in beta 6? Because it’s still crashing for me.

The b6 release notes specified it as a known issue. http://unity3d.com/unity/beta/unity5.2.0b6

Ah ok, I didn’t realize that was the same crash. Thanks!

FYI, should be fixed in the upcoming build.

hello,

my scene crashes on load in latest beta

Latest is still b6, the one makeshiftwings mentioned. So, the fix is not out yet.
However, it’s not clear if this is a different bug or not - have you submitted a bug report and share the bug number?

no but I will real soon

hello when will the next build be released?

Does anyone know if this crash is still present in RC1? It takes forever to upgrade my project from 5.1 to 5.2 and then revert, so I’d rather not bother if it’s already known that this fix isn’t in yet. I didn’t see it mentioned in the release notes.

It’s fixed. Or at least this stack presented in this thread. If it’s still showing issue for you, we’d like to know.

For testing upgrades, I’d recommend copying your project to another folder and test the upgrade (assuming you have the space)

Not sure if it is the same bug but my project still got crashed 100% of time when enter play mode (5.2.0f1)

I tested my project and it no longer crashes, so it does seem like my particular case was fixed. Thanks!

If you have a case number for this crash, please post it here and we will take a look. It’s likely to be a different crash than all the ones reported here (which should be fixed in the RC 1 build)

Getting a crash on play in the f1 release, downloading f2 in case it’s been fixed, but this was our first attempt at updating from 5.1 (which seems to have introduced a bug with Screen.SetResolution on iOS which wasn’t present in 5.0)

Bug #721804

For us, it only happens when we’re trying to load from asset bundles; if I use editor simulation of asset bundles, everything is fine.