I see the following crashes in Windows 10 Store dashboard , they give the following stack trace. How do I diagnose this and is this in the UnityPlayer code ?
I ticked the box for generating the pdb files when I generated the bundle for the store. In the store dashboard I can see the symbol files under current packages. But there is no unityplayer in them. I also do not know how to use it , how to load it ? , can you point me to what needs to be done to isolate this ?
After you download the crash dump from the dev center, open it up in VS. After that, press “start debugging”. Look at the callstack window. You’ll should see a similar view to the one you posted. Right click on any frame that comes from UnityPlayer.dll, and press load symbols. It will ask you to locate the PDB file. They come in Unity’s installation folder, but to tell you the exact place you’ll need to tell me the scripting backend you used, the SDK you targeted and the CPU architecture for the crash.
I sort of understood your explanation but I would need the memory content to debug that. Do you know if Microsoft dashboard provides that ? Do I need to enable anything to get it ?
I cannot see them anywhere only reports about them , for now I would assume that they did not get generated, I will keep my I open and reply to this thread when I get one
I have a similar problem, PDBs are included but it’s impossible to get any useful information from the Dev Center stacktraces.
Seems like crash dumps are no longer available:
“Note that the .cab files currently available in Dev Center are no longer included in the unified Dev Center, instead this functionality is offered in the new Failure Logs in the App Health page and matches the information that used to be accessible through .cab files.”
Hi noob101…
You are correct that crashdumps are not available… The portal should have the stack traces that reflect what the crash dump would… seldomly, I do see apps where the symbols indexing is not right and you get empty stack traces… If you ping me directly [jaimer at microsoft] and are willing to exchange appid details… we can have one of our folks look into it…