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

[Armin Müller]

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

Answering Rik' question:


>> x = ones (15153, 20127, "logical");
>> whos
Variables in the current scope:

   Attr Name        Size                     Bytes  Class
   ==== ====        ====                     =====  =====
        x       15153x20127              304984431  logical

Total is 304984431 elements using 304984431 bytes


In reference to Philip:

It is true that my Octave installation is compiled as 32bit. So the 16GB
memory are useless for that purpose.


>> octave_config_info ("USE_64_BIT_IDX_T")
ans = no


But anyway, either there *is* enough memory and the script should run to the
end. Or it should complain about insufficient memory and return to the command
line. I find it unsatisfying to interpret a crash as "Works For Me". Probably,
the issue is that 15k x 20k "logical" fit into memory very well. But matrix
size is limited to approx. 9k x 9k "double" or 14k x 14k "int32". IMHO, there
is some check within imread.m / __imread__.m / __magic_read__ that does not
respect different memory requirements for different types.


>> x = ones (15153, 20127);
error: out of memory or dimension too large for Octave's index type



    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Nachricht gesendet von/durch Savannah
  http://savannah.gnu.org/