[Octave-bug-tracker] [bug #55427] save -v7 exits with "error compressing data element"

[Philip Nienhuis]

Update of bug #55427 (project octave):

                 Release:                   5.0.1 => dev                    

    _______________________________________________________

Follow-up Comment #3:

It may well be a Windows-specific thing:

GNU Octave, version 6.0.0
:
Octave was configured for "x86_64-w64-mingw32".
:

>> x = rand (1e5, 1e3);
>> save -v7 foo.mat
error: save: error compressing data element
>>


While saving, RAM usage goes up ~1.5 GB before "save" gives up; total max RAM
in use by all processes = 5.11 GB out of 8 GB available so I surmise OOM
wouldn't play a role.

But:

>> x = zeros (1e5, 1e3);
>> save -v7 foo2.mat
>>


goes fine and file foo2.mat is about 760 KB.

@Rik comment #2:
I doubt whether it is directly related to the specific file format. If the
nested struct array is just smaller, yet complexity is the same, it'll work
fine. AFAICS it's just the data object size that matters.

FTR, Octave is configured with --enable-64 and fortran 64 indexing (can't find
the latter literally in  __octave_config_info__ , I only see
'F77_INTEGER_8_FLAG=-fdefault-integer-8').

I have a feeling that thus bug isn't so much Octave's fault but rather due to
the compression library on MinGW that is invoked by Octave.

(Release => dev)

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?55427>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/