[Octave-bug-tracker] [bug #58790] Octave closes unexpectedly when memory allocation fails

[Markus Mützel]

Update of bug #58790 (project octave):

                Category:               Libraries => Interpreter            
                  Status:                    None => Confirmed              
        Operating System:       Microsoft Windows => Any                    
                 Summary: [MXE Octave] Windows 32bit build closes unexpectedly
while running the test suite => Octave closes unexpectedly when memory
allocation fails

    _______________________________________________________

Follow-up Comment #15:

That assignment tries to allocate about 800 MiB in memory.
IIUC, for 32bit programs the allocation size is limited by the maximum
contiguous free memory "block". Currently Octave's "memory" function doesn't
probe the size of that chunk but only return the total free memory (in all
"blocks").

To reproduce this bug, it might be that it is necessary to "sufficiently"
fragment the memory layout and then try to allocate a memory block that is
larger than the largest contiguous memory block.

Matlab fails (or since it is no longer available as a 32bit executable "it
failed") with an error in this case.
It looks like Octave doesn't handle that error gracefully.
It's interesting that gdb isn't able to catch that kind of error.

AFAICT, that kind of error isn't limited to 32bit *Windows* but could happen
on any 32bit OS.
It is likely that a similar error could happen (for much larger arrays) on
64bit OSs, too.
I don't have access to a 32bit Linux to confirm that. But I'll change the
title and flags of this bug anyway.

    _______________________________________________________

Reply to this item at:

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

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