Is anyone else crashing like crazy in 5.6 beta?

EDIT: it now randomly works with regular build, not sure what was done differently – however, it still does NOT work with Vulkan, described further in a reply below. It still crashes in the same spot – during splash screen. It works for me (Intel+NVIDIA), but not my teammate (AMD GPU/CPU). Yes, drivers are up-to-date.

Since the beginning of 5.6 beta, we reverted back to 5.5 – we tried it again now and still crashing like mad.

Anyone else crashing in the exe builds?

SymInit: Symbol-SearchPath: ‘.;C:\Users\Dylan\Desktop\ToL;C:\Users\Dylan\Desktop\ToL;C:\WINDOWS;C:\WINDOWS\system32;SRVC:\websymbolshttp://msdl.microsoft.com/download/symbols;’, symOptions: 530, UserName: ‘Dylan’ OS-Version: 10.0.14393 () 0x100-0x1

Then some “VertexOutputForwardBase” errs, whatever that means.

It could very much be something from the Unity store, but we have so many already – is there a 5.6 compatibility tester? Seems like it could be our shader that’s using code from Unity Standard Shader, which … does’t seem to be working anymore :confused: just a guess, so far … I’d love some assistance :slight_smile: let me know what you need

Can you post the full editor log?

Same here! I’m experimenting with some basic network stuff and everytime I hit “Stop(X)” on the network hud (as a client) it crashes, also in a build.

Could you please file a bug report with a reproduction case?

We already downgraded - it’s unusable for us :confused: if I have time I’ll grab it back for logs

We have found an issue causing a memory corruption that would later make the editor crash in various parts of the code. This should be fixed in the next release. However, we count on our beta users to report these crashes so we can ensure that there aren’t more cases than we already addressed.

Thanks for your collaboration!

This is great, but it’s not just the editor crashing. Exes will also crash –

I saw the above people mention networking. We’re also a networked game! We use Photon. I wonder if the other guys use Photon too?

EDIT: It only crashes at places it tries to spawn things. Reproduced by a teammate, so it’s not a PC issue.

Just a bump for the crashing exe (NOT editor) error with more details:

SymInit: Symbol-SearchPath: '.;C:\Users\Dylan\Desktop\ToL;C:\Users\Dylan\Desktop\ToL;C:\WINDOWS;C:\WINDOWS\system32;SRVC:\websymbolshttp://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'Dylan'

Error occurred at 2017-03-18_111904.
C:\Users\Dylan\Desktop\ToL\ToL.exe, run by Dylan.
69% memory in use.
0 MB physical memory [0 MB free].
0 MB paging file [0 MB free].
0 MB user address space [2371 MB free].
Read from location ffffffff caused an access violation.

It does the splash screen, then it’s black for a few minutes, then crashes
LOG DUMPS >> https://drive.google.com/open?id=0B2FgqC2Y-clga0R0WGFQZlF0M0U

EDIT: Admin mode allows it to WORK (Win10)! However, why would it only work with admin? When someone installs the game, is the shortcut admin by default? I’m going to guess no… this would cause tons of issues, right?

EDIT 2: It randomly works now without admin. Not sure what it does. HOWEVER, same crash when he’s using Vulkan. He said he submitted a bug within Unity. I can run fine with my Intel+NVIDIA, but his higher-end AMD’s (CPU/GPU) are still crashing at same point (during splash screen) without error. Yes, drivers are up-to-date.

Actually, I just crashed without an error repeatedly. It seems that as soon as I build, it works – the next time it runs, it crashes without error. So weird. Looking at the log files, is this an error or warning?

Vulkan PSO: cache data not found [path=C:/Users/KENSHI~1/AppData/Local/Temp/Imperium42™ Game Studio/Throne of Lies®/vulkan_pso_cache.bin]

^ I am wondering if having ™ and (R) affect things – I didn’t realize that’s what outputs the path. Perhaps I should take these out?

This seems like the real err - the last in the log file:

Vulkan PSO: Failed to open pipeline cache data file for writing path[C:/Users/KENSHI~1/AppData/Local/Temp/Imperium42™ Game Studio/Throne of Lies®/vulkan_pso_cache.bin]

Gonna try taking off unicode path. See how it did :tm: at the end of the path?

Just for the record, mine stopped crashing, it was crashing the exe when I was clicking “Stop (X)” - sometimes - in the network manager hud, but I stopped using it and started to use a modified version of the lobby manager that Unity provides.

Could you please reference the bug report # in here so we can check? Does it still happen with f1?

Glancing at the logs (though only to be mildly trusted) it seems to be crashing in liboni.dll which I’m assuming is something else added on (cloth?). It would be a little tough to debug ourselves without those dll symbols. Guessing it maybe a case of a race condition trying to access some data that has already been destroyed, but not sure if it’s a lifecycle issue from our side or through the 3rd party library or the game code itself?

@ Although we do use Obicloth 3, he reports crashing in even an empty scene. I personally don’t crash while actively using Obicloth 3 with f1.

I’ll try to get that report # for you (it was his report, not mine – we both have the same first name, so don’t be fooled haha)

EDIT: We JUST got f1, but I still think he crashes. I’ll get back to you.
EDIT 2: YES, crashes in f1 @LeonhardP

I’m experiencing seemingly random crashes, but can’t reproduce them in new projects. Things like typing in the project search field, crash, clicking a the “window” menu, crash in “validating Lighting menu”. I’ll be uploading repro cases as soon as I get them narrowed down, it’s just hard to find something when there’s already quite some stuff in a project and I don’t want to upload 600 mb of unrelated junk.

Which beta version? We had a spurious memory stomping crash before b11. If you’re using the preview progressive lighting, the memory stomp could occur before f1.

Yes, I’ve found it crashed every time just click play button or click anything then crash.
Only Unity 5.6.0b10 is not crash. It’s good that I’ve backup my project first then I rollback to use Unity 5.6.0b10.