Jim error.log output_log.txt
windows 10 64 bit8gb of ramprocessor amd fx(tm) 6350 six core 3.9ghzamd radeon r7 200 seriesbuild v1.5.0f13
Very good response, thanks for taking the time to reply.
Sorry to hear that, I've taken a quick look at the output log unfortunately it seems Unity failed to capture a full stacktrace.
RtlLookupFunctionEntry returned NULL function. Aborting stack walk.<Missing stacktrace information>
This might make it hard to diagnose the cause of the crash but I will pass it through to code anyway to see if they can spot something.
I can't promise a response until the new year though as we're all currently on XMas leave (But here I am anyway! ;) )
Stefan Furcht, I had a look at the log, the json errors should be fixed since the report, but there are a few other errors I'd like you to have a look at.
The final crash was caused by the Mono-Runtime which should never happen."mono.dll caused an Access Violation (0xc0000005) in module mono.dll at 0033:08e51703."However the exceptions in your log did likely trigger this problem indirectly.The save file seems corrupted and might be broken.However we fixed all the exceptions were we could handle them.So it may not crash anymore but might still cause issues (as there are even blocks missing which can only happen due to corruption of the save file).Let us know if you get any issue with a newly created save files after the next patch is out.
Leveres av UserEcho