[Octave-bug-tracker] [bug #65669] Cell array construction is memory-intensive

[Arun Giridhar]

Follow-up Comment #26, bug #65669 (group octave):

I'm glad that solution works out for you to make the OS show the freed memory.
There doesn't seem to be a direct equivalent of the C function malloc_trim in
C++17, so it cannot be added as is to Octave core itself, but your solution
will be available in this bug report.

If I understand, the reason only Cell types show this problem is because of
the construction of a large number of temp objects during cell array
construction that are freed correctly but the OS thinks it knows better. With
other data types, it's one big allocation, above the glibc threshold, so it
does get returned correctly.


    _______________________________________________________

Reply to this item at:

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

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