RE: size too large for range of Octave's index type

[William Krekeler]

I ran into this same error. The best answer I got was that the error is caused by Windows program memory space and the way that Octave memory is allocated. I have not found a work around or the exact answer. Note, I did try switching from Octave to Octave in cygwin but that test also fails as I realized cygwin is only available as a 32 bit binary for windows regardless of whether or not you are running a 64 bit OS.

 

See help list “Octave Memory Exhausted Error” between 11/3 and 11/5/2010 for more information.

 

Let me know if you figure it out as I haven’t had time to return to this problem.

 

Bill Krekeler
Electro-Optics Engineer
CET, LLC
address@hidden

 

From: Tim Rueth [mailto:address@hidden
Sent: Thursday, December 02, 2010 12:45 AM
To: address@hidden
Subject: size too large for range of Octave's index type

 

I hit this problem a while back, and fixed it by changing my double-precision vars to single precision.  But now in my current sim, my ndgrid matrices are so large, even with single precision, that I'm getting the following error again:

 

error:  memory exhausted or requested size too large for range of Octave's index type

 

After getting this error, I did a "whos" and got:

 

421605065 elements using 1515209069 bytes

 

Okay, that's 1.41 GB.  What is Octave's limit?  In reading previous posts, it looks like Octave's limit is 2e9 elements or 2GB, but I'm not sure what build this refers to, in case later builds support more.  I'm running version 3.2.3 on Win7 w/6GB of RAM.  I also tried it on 3.2.4 and got the same error.

 

Thanks,

 

--Tim