An unhandled exception of type 'system.stackoverflowexception' occurred in mscorlib.dll

Question

1.00/5 (1 vote)

See more:

Hi ,when i run my project this error is coming
I am using Visual Studio 2017 Community
Please help me.

Error is

An Unhandled exception of type 'system.stackoverflowexception' occurred in mscorlib.dll

What I have tried:

Any project i am running it is throwing same error

Posted 30-Oct-18 3:37am

Mukund M

Updated 30-Oct-18 4:46am

Add a Solution

Comments

F-ES Sitecore 30-Oct-18 10:49am

It means your code is doing an infinite loop somewhere.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dirk Bahle · Answer 1 · 2018-10-30T04:47:00

A StackOverflowException indicates that you are running code that has a method or property call that call itself (directly or indirectly) recursively.

1) Activate Exceptions to be shown be checking all types of Common Language Runtime Exceptions at:
Debug > Exceptions

Execute in debug mode - does VS break at a relevant place?

No?

2) Use the Debug > Windows > Call Stack (at debug time) to review the calls that are leading towards the exception.

3)
Share your code if you cannot find the source of your problem since there are no mindreaders here I am afraid...