Crash on windows store after updating unity from 4.5.0 to 4.6.2p2 (579085)

News & General Discussion
1

Hi. Getting app crashes on windows store after updating unity from 4.5.0 to 4.6.2p2.

After downloading .cab file from dashboard and opening it with WinDbg.exe (and setting symbols path to /Players/x86/master, where UnityPlayer.pdb is located, I’m getting this (with !analyze -v):

STACK_TEXT:
0477f87c 5a7658a3 0477f8d8 00000000 5ace7e2f UnityPlayer!DebugStringToFilePostprocessedStacktrace+0x2d3
0477f91c 5a68774d aaaaaaaa 00000000 5ace7e2f UnityPlayer!DebugStringToFile+0x133
0477f9c8 5a687567 aaaaaaaa 5aed85d0 aaaaaaaa UnityPlayer!MonoManager::MonoManager+0x1bd
0477f9f0 5a593c53 aaaaaaaa 00000000 00000000 UnityPlayer!MonoManager::pRODUCE+0x57
0477fa18 5a71d003 aaaaaaaa 00000000 047849c8 UnityPlayer!Object::produce+0x43
0477fab4 5a71696c aaaaaaaa 0000000c 00000000 UnityPlayer!SerializedFile::ReadObject+0x83
0477fafc 5a599e41 0000000c 00000074 0477fb68 UnityPlayer!PersistentManager::ReadObject+0xac
0477fb30 5a5a58a6 00000074 5aeddb04 0000000c UnityPlayer!PPtr::hushed:perator Object *+0x71
0477fb48 5a5a5bcb 0448c810 00000320 0448d0b8 UnityPlayer!LoadManager+0x46
0477fbb8 5a6f486c 0448d0b8 aaaaaaaa aaaaaaaa UnityPlayer!PlayerLoadGlobalManagers+0xcb
0477fc00 5a9a685e 04382728 00000000 772e154d UnityPlayer!PlayerInitEngineGraphics+0x8c
0477fc8c 5a9aee6e 0477fcd4 5a9a2a6a 0448d0b4 UnityPlayer!<lambda_6bfda1077b76cb51151543033db355b2>::hushed:perator()+0x45e
0477fc94 5a9a2a6a 0448d0b4 00000000 006d0a00 UnityPlayer!Platform::smile:etails::__abi_FunctorCapture<<lambda_6bfda1077b76cb51151543033db355b2>,void>::Invoke+0xe
0477fcd4 5a9a2aeb 0477fd08 5a9cebd4 04382728 UnityPlayer!UnityPlayer::AppCallbacks::_AppThreadImplementation+0x8a
0477fcdc 5a9cebd4 04382728 00000000 00000000 UnityPlayer!UnityPlayer::AppCallbacks::_AppThread+0xb
0477fd08 5a9d006f 006d09fc 0477fd40 5a9cf1bf UnityPlayer!<lambda_ccf6584601e785dcb0d98612145af013>::hushed:perator()+0x34
0477fd14 5a9cf1bf 006d09fc 009fbd08 00000000 UnityPlayer!Platform::smile:etails::__abi_FunctorCapture<<lambda_ccf6584601e785dcb0d98612145af013>,void,Windows::Foundation::IAsyncAction ^>::Invoke+0xf
0477fd40 6ee54a29 006d09e8 009fbd08 00000000 UnityPlayer!Windows::System::Threading::WorkItemHandler::[Windows::System::Threading::WorkItemHandler::__abi_IDelegate]::__abi_Windows_System_Threading_WorkItemHandler___abi_IDelegate____abi_Invoke+0x3f
WARNING: Stack unwind information not available. Following frames may be wrong.
0477fd60 6ee54a97 6ee54a7c 772e179b 0477fd7c threadpoolwinrt+0x4a29
0477fd70 772e17ad 009fbd08 0477fdc4 77dc32b1 threadpoolwinrt+0x4a97
0477fd7c 77dc32b1 009fbd08 aaaaaaaa 00000000 kernel32+0x17ad
0477fdc4 77dc327f aaaaaaaa 77def080 00000000 ntdll+0x532b1
0477fdd4 00000000 6ee54a7c 009fbd08 00000000 ntdll+0x5327f
FOLLOWUP_IP:
UnityPlayer!DebugStringToFilePostprocessedStacktrace+2d3 [c:\buildslave\unity\build\runtime\utilities\logassert.cpp @ 1051]
5a7656f3 cc int 3
FAULTING_SOURCE_LINE: c:\buildslave\unity\build\runtime\utilities\logassert.cpp
FAULTING_SOURCE_FILE: c:\buildslave\unity\build\runtime\utilities\logassert.cpp
FAULTING_SOURCE_LINE_NUMBER: 1051

Any suggestions?

I cannot reproduce it on my PC. But amount of users who run into it is huge.

2

Hi,

that’s an extremely strange issue… it would point to corrupted UnityEngine.dll in downloaded game (that’s what the stacktrace is telling - that path happens when it fails to load metadata from UnityEngine.dll). Have you tried downloading the game from the store yourself to see if it works?

Another solution to try would be to rebuild the game and submit it to the store again, hoping it would fix the issue.

Are you targeting Windows 8.0 or 8.1?

3

Thanks for the answer, I’ve moved the theme to support forum Crash on windows store after updating unity from 4.5.0 to 4.6.2p2 - Unity Engine - Unity Discussions (this is a wrong forum clearly)

I’m targeting 8.1 windows
It works for me when I install it from the store

I gave a lot of information to another theme, if you need it