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.
jonaszell
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Post
Replies
Boosts
Views
Activity
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.