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

[Armin Müller]

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

I've tried the "large indexing" version of Octave. Everything runs fine.
That's the good point.

Unfortunately, I've also tried to fathom the maximum image size allowed in
this version. Typing

x = ones(50000, 50000);    % ~18.6 GB

did lock up my system completely. No warning, no error, just endlessly
swapping memory on the HD, not even the task manager did respond. I had to do
a "hard" reboot.

As written below, 14k x 14k "int32" = 0.73 GB is the maximum I can get on the
32 bit system. Alternatively 9k x 9k "double" = 0.60 GB. The exact value
varies, it seems that it is heavily depending on the preconditions if the
memory is absolutely "clear" and Octave started newly, or if it is "used". But
both values are far less than I would expect.

    _______________________________________________________

Reply to this item at:

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

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