Memory out of range exception

Question

0.00/5 (No votes)

See more:

Hi ,
In my application i am using very big lists of points i.e.

C#

List<point> Lst=new List<point>(1008000);

I am creating 25 such big lists. But unfortunately CLR throws out of memory exception.
Please let me know how i can handle this issue.
[edit]Code block added - OriginalGriff[/edit]

What I have tried:

I already googled and found that compiling as x64 solves the issue, but i do not want to change application to x64. Is there any other way to handle memory out of range issue.

Posted 9-Aug-16 9:06am

RhishikeshLathe

Updated 9-Aug-16 19:34pm

OriginalGriff

v2

Add a Solution

Comments

Kenneth Haugland 9-Aug-16 15:18pm

Split your list up in smaller lists, or create your own that does this for you.

ZurdoDev 9-Aug-16 16:23pm

Add memory. Optimize code. Change what you are doing. What other options might there be?

njammy 9-Aug-16 16:29pm

Consider distributed processing via multiple services/transactions and keep track using a more efficient model.

Ramza360 9-Aug-16 16:54pm

Try virtualization with a data source.

Beginner Luck 9-Aug-16 21:17pm

x32 bit and x64 bit of understands int is different. example int is in x32 is int32 and in x64bit is int64. if you use database you know the limit contain is different as int x64 more than int x32bit
http://stackoverflow.com/questions/5812406/16-bit-int-vs-32-bit-int-vs-64-bit-int

Patrice T 10-Aug-16 1:43am

Can you tell us what you do with this data ?

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)

Mehdi Gholam · Answer 1 · 2016-08-09T19:34:00

On x86 machines (32bit) the memory is limited to 4gb total of which the OS takes 1gb which leaves theoretically 3gb for apps but practically you are limited to 1.8gb-2.5gb depending on your hardware.

If should strongly rethink keeping a lot of data in memory unless there is a very good reason for it, blocking/chunking data is much more efficient in most cases and you will not be limited by your hardware.

Look at Key/Value data stores, or even relational databases which were designed for handling data.