Hello there!
I am confused about the situation that my project now tends to crash around 5 to 20 minutes after startup. Either this blackscreens my computer and I need to restart, or I get this error message:

There are only two changes I believe that could cause the error. (Unless it’s not my fault, but I assume it is.)
Possible cause A: flag shader
I had previously implemented a flag shader graph for countries in my strategy game, for which I followed this official Unity tutorial (I am new to shaders creation): https://learn.unity.com/project/make-a-flag-move-with-shadergraph
With the next version I wanted to improve the flag shader. This is the new shader graph I created:
Could it be, that this shader graph causes the error? If so: why? It does not look especially complex or as if it would have a potential infinite loop in it to me.
Possible cause B: render texture and second camera
The other change I believe to possibly be the cause is, that I am using a second camera to create a render texture that I am showing on a RawImage in a UI element. I heard that this may be heavy on the GPU, but I thought I had taken measures to ensure this shouldn’t happen, by making it so that the second camera only renders the one object that it focuses on and nothing else.
(The flag in the background is rendered onto a transparent render texture in front of an image of the sky.)
Do you know what is the likely cause of the issue? Do you have an idea that could help me? Please let me know.
Edit 1
I tested running it without the flag shader and it still crashed, so I assume it is less likely to be causing the issue.
Edit 2
It appears that the crashes are not happening when I disable the second camera. Could someone explain why having a second camera can cause this?
Edit 3
I found my answer. It appears that I had the same issue as the person who posted this: https://forum.unity.com/threads/unity-2022-3-2f1-urp-render-texture-from-camera-is-crashing-the-application.1453870/ - It was a Unity bug that was fixed. I updated to Unity version 2022.3.33, and now I don’t have the problem anymore.

