ERROR " A first chance exception of type 'System.OutOfMemoryException' occurred in PresentationFramework.dll"

Question

0.00/5 (No votes)

See more:

Just wondered if you could please help me with this: I had my code working in a couple days, but as I tried running it as for today..it keeps giving me this ERROR " A first chance exception of type 'System.OutOfMemoryException' occurred in PresentationFramework.dll" This is a WPF Application and I get this Error in all the pages. I tried Memory Diagnosing tool...but there no problem with the memory. Everytime I debug..the solution uses a high amount of memory.. please Help

![This is what I get when I run the solution, it brings this error in almost all the pages every time they are initialized ][1]

[1]: http://i.stack.imgur.com/AnPZ0.png [1]

Posted 11-Aug-14 5:30am

Member 10007566

Add a Solution

Comments

[no name] 11-Aug-14 11:40am

Why would you think that there would be a problem with your memory? Your application is simply using up all of the memory allocated to it.

Member 10007566 11-Aug-14 12:01pm

As I go throgh forums, i got to the one that talked about using "Memory diagnostic tool"; would you please elaborate your answer...

[no name] 11-Aug-14 12:10pm

There is nothing to "elaborate" on. You are allocating so much memory in your program that you are using up the available memory. Why is that so hard for you to comprehend?

Member 10007566 11-Aug-14 11:54am

HOW to fix that?

[no name] 11-Aug-14 11:57am

You would fix that by not using so much memory.

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)

Dave Kreskowiak · Answer 1 · 2014-08-11T06:35:00

Just by the error message it is impossible to tell you what's wrong. There are a thousand different ways for you to run the machine out of memory.

But, usually, this is because you either:

A) Allocated objects but never released all references to them and continued to allocate more objects, thereby running the machine out of memory,

B) You're not calling Dispose on objects that you really should be calling Dispose on. As a rule of thumb, if an object has a Dispose method, call it when you're done with the object!