|Subject:||RE: "out of memory or dimension too large for Octave's index type"|
|Date:||Tue, 16 Jan 2018 17:55:13 +0000|
Thanks for the help. I ran into ‘out of memory’ issue even more when I was using octave 4.0.0. Actually it’s why I upgraded to 4.2.0.
From: Help-octave [mailto:help-octave-bounces+address@hidden
On Behalf Of Ian McCallion
In case it helps, I have had one or two unexpected occurrences of this message, but only since 4.2.0. I did not try to track down the source of the problem and worked around it. I'm afraid I associated it with an increased frequency of octave crashes that started at about the same time. I'm using win10 home.
Yan, can you try using Octave 4.0.x to see if that solves it?
On 16 Jan 2018 2:34 pm, "Francesco Potortì" <address@hidden> wrote:
>>I got this "out of memory or dimension too large for Octave's index
>The size of the matrix is 160MB, nothing to do with 64 bit indexing.
>Restarting octave is not an option as the "out of memory" issue happens
As also Philip was suggesting, have you considered rebooting your system
As far as I understand, memory fragmentation is a system problem on
|[Prev in Thread]||Current Thread||[Next in Thread]|