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

[Philip Nienhuis]

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

Sure, I agree that Octave shouldn't crash.
But AFAIU out-of-memory errors are extremely hard to catch. In my own
experience, processes that hit this kind of error are often doomed to crash
sooner or later.
But maybe the core Octave devs know a trick.

As to "works for me" - the solution -a 64-bit indexing Octave- does work and
that is what counted in my perception. 
Unfortunately for you that solution is yet out of reach for you.
Hopefully a 64-bit & 64-bit indexing Octave for Windows will be available
soon.
Using mxe-octave, it can be built OOTB these days by about anyone.

BTW, in the majority of cases memory fragmentation is far more important then
plain amounts of installed RAM. Even on my 8 GB RAM laptop I've hit OOM errors
when reading extremely large files even when it looked like there was
sufficient free RAM.



    _______________________________________________________

Reply to this item at:

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

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