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

[Philip Nienhuis]

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

Slightly OT but related tot RAM usage:

At work we run the network installation of Matlab in a "bubble", a sort of
virtual environment.
That gives considerably better results as to RAM usage (but don't get me
started on CPU performance :-) ):

>> ver
------------------------------------------------------------------------------------------------
MATLAB Version: 7.14.0.739 (R2012a)
MATLAB License Number: ******
Operating System: Microsoft Windows 7 Version 6.1 (Build 7601: Service Pack
1)
Java Version: Java 1.6.0_17-b04 with Sun Microsystems Inc. Java HotSpot(TM)
Client VM mixed mode
------------------------------------------------------------------------------------------------
MATLAB                                                Version 7.14      
(R2012a)

<snip>

>> memory
Maximum possible array:            1151 MB (1.207e+09 bytes) *
Memory available for all arrays:   1423 MB (1.492e+09 bytes) **
Memory used by MATLAB:              357 MB (3.744e+08 bytes)
Physical Memory (RAM):             4096 MB (4.295e+09 bytes)

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


(compare to the results in comment #13)

Maybe that can be made into a useful hint (I cannot actually confirm it here)
to get max. array sizes: i.e., to run Octave in a virtual machine in a guest
environment stripped down to the bare minimum required to run user programs.

When I get time for it I'll put something about RAM usage and OOM errors on
the wiki.

    _______________________________________________________

Reply to this item at:

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

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