[Octave-bug-tracker] [bug #43495] Crash when reading large TIFF with imread()

[Philip Nienhuis]

Follow-up Comment #13, bug #43495 (project octave):

@Armin:
"..far less than I would expect"....  Well I have some less rosy info for you
then ;-)

To illustrate what I wrote at the bottom of comment #6, here's some output
from Matlab r2014b prerelease on my WinXP 32bit box w. 4 GB RAM:

Just after starting up WinXP, first ML command:

>> memory
Maximum possible array:    354 MB (3.715e+08 bytes) *
Memory available for all arrays:   1358 MB (1.424e+09 bytes) **
Memory used by MATLAB:    403 MB (4.227e+08 bytes)
Physical Memory (RAM):   3324 MB (3.485e+09 bytes)

*  Limited by contiguous virtual address space available.
** Limited by virtual address space available.
>> 


and after some work:

>> memory
Maximum possible array:    277 MB (2.901e+08 bytes) *
Memory available for all arrays:   1285 MB (1.347e+09 bytes) **
Memory used by MATLAB:    456 MB (4.786e+08 bytes)
Physical Memory (RAM):   3324 MB (3.485e+09 bytes)

*  Limited by contiguous virtual address space available.
** Limited by virtual address space available.
>> 


For comparison, Octave 4.1.0+ CLI allowed me to squeeze a double array of up
to 8341x8341 into memory, max. 556 MB (or MiB?).

(To be honest, these results disappoint me, I had expected max. array sizes
would be 600-700 MB. But: no.)

In conclusion I think you're even quite lucky to get 0.73 GB arrays into
Octave on a 32-bit system .... (but on the bright side: Octave compares quite
good to the competition...)


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?43495>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/