28,662 questions
.NET Frameworks + VS 2022 Bug - Critical Severity (Resolution for New Guard Page Stack Creation Issue)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(195.2, 25%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERA%3C/text%3E%3C/svg%3E)
Rashid Ali
0
Reputation points
Hello Folks, I'm seeking a little assistance. Whenever I attempt to compile the app in release mode and run it, I encounter this error. Notably, there have been no modifications to the code. I even attempted to compile previous versions of the code, and regrettably, they are also experiencing crashes.
While some might suggest that insufficient memory might be the issue, I can confirm that this is not the case. My computer boasts 32GB of memory, with over half of it remaining unused.
Funny Part is, older compiled versions of the app run smoothly, whereas newly compiled versions of the old code, even without any changes, do not.
I appreciate any insights or assistance in resolving this puzzling issue.
Windows for business | Windows Client for IT Pros | User experience | Other
Developer technologies | .NET | Other
Developer technologies | .NET | Other
Microsoft Technologies based on the .NET software framework
4,107 questions
Developer technologies | Visual Studio | Other
5,457 questions
{count} votes
-
RLWA32 49,641 Reputation points2023-09-13T07:48:44.87+00:00 To obtain an understanding of stack guard pages I suggest you read A closer look at the stack guard page.
Issues arising from a stack guard page are unrelated to the total amount of memory installed in the system. They are related to the amount of memory that is allocated to a thread's stack and how that stack memory is being used. For example, recursive code will generally consume more stack memory than non-recursive code.
Sign in to comment
Sign in to answer