Moving the view to a @ViewBuilder function fixed it for me as well, sadly I wasn't able to reproduce the issue in a clean project.

I don't think that's the problem, since a cycle like that should only be an issue at runtime, right? Personally this issue has become so bad for me that I have to leave activity monitor on constantly on my second monitor so I can see right away when my memory usage jumps up to infinity and force quit Xcode. Most of the time when the issue occurs, no GeometryReader is involved whatsoever. I haven't been able to find any pattern as to what causes it.