out of memory at line

Question

0.00/5 (No votes)

See more:

Hi,
i have two radlistboxes.
I transfer or drag n drop to one-another radlistboxes.
When I click on save button, I got pop up which say " out of memory at line 1022 ".
page doesn't have line 1022.
Record didn't save when this error comes.

Help me.

Posted 25-Jun-13 17:45pm

Sant Osha

Add a Solution

Comments

Suvabrata Roy 26-Jun-13 0:59am

radlistboxs means radiolistBox?

Rajesh Anuhya 26-Jun-13 1:04am

it's thirdparty(telerik) control

Sant Osha 26-Jun-13 1:01am

dude.. its telerik control

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)

Jason Gleim · Answer 1 · 2013-06-25T18:58:00

Without code or any idea of the steps you have taken, it is almost impossible to help you on this. However, out of memory usually means you are out of stack or heap space. Either one is typically because of a loop in your code.

I suggest looking for a place where your operation is triggering an event, which is in turn triggering an event, which is re-triggering the first event and so on. The ui update methods are notorious for this.

Breakpoints and tracing are your friend. You could also try a performance profiler which would zero in on the method causing the problem.