[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #58790] Octave closes unexpectedly when memory
[Octave-bug-tracker] [bug #58790] Octave closes unexpectedly when memory allocation fails (Windows 32bit executable)
Thu, 3 Sep 2020 14:51:09 -0400 (EDT)
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.83 Safari/537.36 Edg/85.0.564.44
Follow-up Comment #20, bug #58790 (project octave):
I'm not sure this is an integer overflow when computing the total array size.
The number of elements in the array that triggers this bug is "just" 100
million (see comment #14). The largest signed 32 bit integer is approximately
Also, the approximately 800 MiB array that causes this bug is still about a
factor 5 smaller than 4 GiB where uint32_t overflows or more than a factor 2
smaller than 2 GiB where int32_t overflows.
Additionally, this only seems to crash Octave if the memory layout is
"sufficiently fragmented". An integer overflow should not depend on how much
of the memory is available if I understand correctly.
But I don't know how the total array size is calculated. So there might be an
intermediate result that overflows?
Reply to this item at:
Message sent via Savannah
- [Octave-bug-tracker] [bug #58790] Octave closes unexpectedly when memory allocation fails (Windows 32bit executable),
Markus Mützel <=