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

[Philip Nienhuis]

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

@Carnë / comment #6:

With a freshly built 3.9.0+ (--enable-64) for MingW, using Markus' patch (bug
#43505), I get similar results as you:

>> tic; img = imread ("Erik_1_6000dpi.tiff'); toc
Elapsed time = 6.85139 seconds.


but then:

tic; imshow (img); toc
Elapsed time = 4.97828 seconds.

and although Octave may be ready, only the outline of the graphics window is
drawn and Octave doesn't return to the prompt, instead the hard disk started
crunching. After half an hour I gave up and killed Octave.
Windows' Task Manager indicated ~6.7 GB of the available 8 GB is used. Even
with "stolen RAM" (video) and drivers address space I think there's enough RAM
available.

Similar goes for "spy (img)"


    _______________________________________________________

Reply to this item at:

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

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