HDRP random crashes

Hey!

Recently I've gotten a lot of crashes in my project which uses ECS and HDRP.
While I'm aware of memory problems and leaks that can sometimes happen in ECS when code is wrong that leads to crashes I'm also getting this with no leaks or errors.

Drilling done on this, HDRP seems to be the root cause and some state of init/reinit because it mostly happens on recompiles or Unity gaining focus again.
Instead of reporting every single crash again and again I'd just like to post it here so someone can look at my 21 crash reports during the last 7 days.

As the file is too big to attach (6.3mb) here's the link: www.enzenebner.com/Unity/Crashes.rar

I've been running on the last 2 versions of HDRP for Unity 2019.1. Sadly the latest update to HDRP couldn't resolve my crashes.

I hope this can be resolved!
Thanks and greetings

 

hey, did you ever solve this issue? I've been having the same problem, unfortunately unity cant reproduce it.
I think it might be due to the post processing that is included with the hdrp package but I'm not sure

 

Are you on the latest version of hdrp? It went away with a newer version, I have 5.16.1

 

hmm, I'm on 6.9.1
with no post processing it seems stable but with post processing it will randomly crash sometimes when I tab back to the editor, I will have to see if I can narrow it down to a specific effect

 

Oh well, I haven't opened the project in a while. Guess what happened when I switched back to it?
It crashed. Guess the error didn't go away.
I don't know what it's about, I have several ECS projects with hdrp running and none are crashing like this. My newer ones are on 2019.3 but previous test projects were on 2019.1 too.

Hope you can find a solution. If all else fails, maybe try 2019.3

 

It is crashing for me and my team randomly as well ever since I started using HDRP, I'm on 2019.2 + HDRP 6.9.1 and it still happens. It occurs more often in the standalone build. Is it crashing for you guys with the same stack trace by any chance?

Mine is as follows:

Code (CSharp):

1. Stack Trace of Crashed Thread 7980:
2. 0x00007FFB71FCB871 (mono-2.0-bdwgc) mono_get_runtime_build_info
3. 0x00007FFB71F51D92 (mono-2.0-bdwgc) mono_perfcounters_init
4. 0x00007FFB71F5AD8F (mono-2.0-bdwgc) mono_runtime_invoke
5. 0x00007FF6A55B9AF2 (Unity) PAL_Thread_YieldExecution
6. 0x00007FF6A55B37B1 (Unity) PAL_Thread_YieldExecution
7. 0x00007FF6A4D396BA (Unity) PAL_Memory_Free
8. 0x00007FF6A4D3796D (Unity) PAL_Memory_Free
9. 0x00007FF6A507D2A8 (Unity) PAL_Memory_Free
10. 0x00007FF6A507D389 (Unity) PAL_Memory_Free
11. 0x00007FF6A50821FB (Unity) PAL_Memory_Free
12. 0x00007FF6A364EA9B (Unity) PAL_Thread_SupportsThreads
13. 0x00007FF6A364C59C (Unity) PAL_Thread_SupportsThreads
14. 0x00007FF6A3EDBE50 (Unity) PAL_Memory_Free
15. 0x00007FF6A3EDE86F (Unity) PAL_Memory_Free
16. 0x00007FF6A6B75792 (Unity) InitializeNvCloth
17. 0x00007FFBD1417974 (KERNEL32) BaseThreadInitThunk
18. 0x00007FFBD39EA271 (ntdll) RtlUserThreadStart
19.  

 

This is the stack trace of my most recent crash, do you use the post processing volume? I've noticed when i have it disabled I don't crash (so far anyway)

Code (CSharp):

1.  
2. Stack Trace of Crashed Thread 9380:
3. ERROR: SymGetSymFromAddr64, GetLastError: 'The specified module could not be found.' (Address: 000001ED5F879200)
4. ERROR: SymGetModuleInfo64, GetLastError: 'A dynamic link library (DLL) initialization routine failed.' (Address: 000001ED5F879200)
5. 0x000001ED5F879200 ((<unknown>)) (function-name not available)
6. 0x000001ED003DAD84 (mscorlib) System.Attribute.IsDefined()
7. 0x000001ED003DAA23 (mscorlib) System.Attribute.IsDefined()
8. 0x000001ED003DA913 (UnityEditor) UnityEditor.SceneView.ComponentHasImageEffectAttribute()
9. 0x000001ED003DB0A1 (UnityEditor) <ReplaceComponentsIfDifferent>c__AnonStorey1.<>m__1()
10. 0x000001ECCF1A13E6 (mscorlib) <Module>.runtime_invoke_bool__this___object()
11. 0x00007FFC30CFBC80 (mono-2.0-bdwgc) mono_get_runtime_build_info
12. 0x00007FFC30C81D92 (mono-2.0-bdwgc) mono_perfcounters_init
13. 0x00007FFC30C8AD8F (mono-2.0-bdwgc) mono_runtime_invoke
14. 0x00007FF679549AF2 (Unity) PAL_Thread_YieldExecution
15. 0x00007FF6795437B1 (Unity) PAL_Thread_YieldExecution
16. 0x00007FF678CC96BA (Unity) PAL_Memory_Free
17. 0x00007FF678CC796D (Unity) PAL_Memory_Free
18. 0x00007FF67900D2A8 (Unity) PAL_Memory_Free
19. 0x00007FF67900D389 (Unity) PAL_Memory_Free
20. 0x00007FF6790121FB (Unity) PAL_Memory_Free
21. 0x00007FF6775DEA9B (Unity) PAL_Thread_SupportsThreads
22. 0x00007FF6775DC59C (Unity) PAL_Thread_SupportsThreads
23. 0x00007FF677E6BE50 (Unity) PAL_Memory_Free
24. 0x00007FF677E6E86F (Unity) PAL_Memory_Free
25. 0x00007FF67AB05792 (Unity) InitializeNvCloth
26. 0x00007FFC8E247BD4 (KERNEL32) BaseThreadInitThunk
27. 0x00007FFC8E40CE71 (ntdll) RtlUserThreadStart
28.  

 

I'm getting crashes a lot as well in HDRP. Happens more in a built Standalone game for me than in the Editor. I'm using Unity 2019.2.6f1. HDRP version 6.9.0. My game has crashed almost every single time I've played it in a Standalone build -- usually after a couple minutes of playing it.

It did seem like losing focus and refocusing causes crashes, as I was switching between task manager and the game, it crashed. But the postprocessing might be doing it as well. I havn't tested extensively yet, I want to try it without postprocessing to see if that helps.

I havn't seen too many solutions. It seems like I'll have to wait for the next dot version of Unity to see if it's more stable. Right now I have yet to get through a full play session without my game crashing -- and I have no idea why.

P.S. Where do you find the stack trace for the game crashes?

 

I'm still crashing quite often in Editor and in Builds with HDRP. Can someone direct me as to where to find the crash reports or stack traces?

All I see in the Game build folder for each build is the "UnityCrashHandler64.exe" and I'm not even sure what that does.

 

Yeah, the log can be in different places depending on what crashed and what your hardware is. This should help: https://docs.unity3d.com/Manual/Log...097.558030228.1574109054-160785489.1529611613

 

As boyd600 mentioned above, it seems to be the post-process volume effects that is causing a lot of crashing for me as well. When I disable it, my game seems stable.

I don't know what exactly in the post-process volume is causing it, but all I know is completely disabling the volume fixes it (for now).

The post-process volume is pretty crucial though for graphics, so I hope it's fixed in upcoming HDRP versions.

 

using Unity 2019.3.4f1, Constant HDRP crashes. I have to save literally every 5 secs just to make more progress on development of my game.... Please fix.

 

I'll send this post over so we can try and get an answer on this!

 

Any news on this? Main feature of a game i'm working on is based on post processing.

 

They have released new unity version recently, which however doesnt fix memory leak. I sent them repro as simple as possible, showing the memory leak. No answer after month.

 

New HDRP version releases soon around mid may.

 

I'm on HDERP 7.3.1 and it has a slew of random bugs and crashes of the Editor and the builds. I had to suggest to my PM we switch our project to legacy rp, until we are too deep in this HDRP-dependent mess.
This tech is not ready. It's not "out of preview". It crashes constantly. Particles and trails are broken.
I love unity, but if nothing changes in a year, i'll have to switch to something other then Unity. I'll have to kiss goodbye my 8 years of skill, that would be not an easy choice.

 

@Lynxed I feel for you, know how your feeling...frustrated. To be honest ive been using HDRP for a little over a year, and have had no problems or crashes. Please remember this month we are supposed to get 2019 LTS, at least check it out. Again HDRP has worked so well, that ive ported my project Jurassic Extinction to HDRP, I have particle effects working, water with underwater caustics, and a great HDRP wind/foliage shader. Ive even broken HDRP a few times, still no crash or probs.

Sorry that you and alot of others are experiencing so many probs, i just dont get it, lol.

 

Good for you. Do you write a lot of custom post processing? If you only use out of the box features, then yeah, maybe it's okay for you.

 

I have experienced a crash. 19.3.12
Using camera and creating the level at some point camera widget was not on the camera. Then it was crash without any warnings about it.