I get many different crashes while working with the latest few 2019.3 betas, but the bug reporter fails out after a few minutes with “error -1 failed to read file” or similar. So of course I can’t submit bug reports. I’m including my entire project with it because that has been stated as the best way to get things fixed. If I don’t include the project, it works.
If the project is a few giga-bytes, the bug reporter tool often fails.
In this case my approach is to submit a bug-report without attaching the project, but asking QA to reply with a password protected Unity owncloud link. Let QA know the amount of space you need to upload your project as .zip archive.
Then submit your reports as usual, without attaching the project, but referencing the Case number from the bug-report where QA provided the owncloud location, so they can access your project.
In such cases (and this error message), I was able to send the report if I included only the “Assets” folder and separately (another ‘Add Folder’) the “ProjectSettings”, “Packages” etc. if needed. I guess (and I might be wrong) it doesn’t like the Temp folder or perhaps Library, too.
I usually don’t send entire projects unless they’re minimal repro projects, or are small to begin with – but if the whole project is needed to reproduce the bug, I think what Peter77 is suggesting is the best approach.
I did what you guys suggested, and uploaded my project to a link provided by Unity QA. Their response was “we can’t repro this so we’re closing it”. The problem is this: 2019.3 crashes multiple times per day, whereas previous versions crashed once every few weeks. It does it intermittently, without any obvious pattern, at least not to me. Clearly, something is broken compared to previous versions, and I’d like to contribute to getting it fixed. Doesn’t Unity get any info from crash dumps so they don’t have to rely on people like me saying “well I hit Play and then exited Play mode and it crashed…”?
I had crashes like those – when hitting Play, exiting Play – or simply the Editor froze and started ‘Not Responding’ forever (in Task Manager). The crash errors were whatever from “d3d11: Failed …” or “AccessViolation”.
The only recurring pattern for me was “keeping the Editor open for too long”. I don’t know if it’s your case as well, but it sounds similar. This is the resolution note I received:
Well, I didn’t try increasing the timeout, but I stopped leaving the Editor open in the background (or “hibernated” overnight) when I’m not directly using it and the crashes became less frequent. But as I said – you may or may not be experiencing the same issue.
That’s a new one to me, thanks for posting it. Typically I do leave Unity running for days at a time. However, with 2019.3 it’s unfortunately not the issue because it crashes multiple times per day.