Trying to make sense of this crash report

Unity Engine
1

I’ve been working on this VR project that uses VRTK. Everything I have done some far works within the editor, but when I make a build and run the executable the program crashes. Initially there was a DllNotFoundException which was due to the fact that the architecture was set to X86 (I think). Since changing it to X86_64 I do not get the error, however the executable still crashes. I’ve re-imported all the VR related assets but that didn’t resolve anything. I was wondering if someone could help me understand how to read the crash log better, I’m guessing there’s a problem script that I’ve done but I am unable to find it.

Currently running on Unity 5.6.0f3. I’ve held off updating to 2017.2 since I didn’t want to risk breaking my scripts, but I’ll make another copy for now.

Here’s the log:

2

Maybe try: Reddit - Dive into anything

3

Project converting over to 2017.1 but I’ll try that. Thanks

4

Seems like it may be more the issue discussed here U5.3 - ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.'

5

I saw this earlier in the day, can’t see any solutions other than converting to 5.6.1. Converting to 2017.1 broke something in that Unity couldn’t find certain scripts. I’ll revert back to an earlier copy and try changing the graphics settings

6

I think the thread and perhaps the other linked should be read as people changed random things and the bug potentially went away for them due to the changes (but not necessarily because of the specific change).

The real info in the linked thread for me (besides more random things to try like different versons of Unity) -

Try to find Unity’s ticketting system and find if since the first report from the Dreamfall Chapters team(?) if anyone raised a bug and what it’s status is

Follow this advice to get a better stacktrace for the crash

Are you crashing in the memcopy routine, if so check if maybe any of your local packages may be broken/truncated? Seems like a longshot in your case (local development files)

Post in that thread/on the bug report, if open, with any real info you can get describing the issue, including the real stacktrace for the crash and what you have tried, including changing versions.