[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Hg200
Subject: [Octave-bug-tracker] [bug #58790] Octave closes unexpectedly when memory allocation fails (Windows 32bit executable)
Date: Sun, 2 Aug 2020 06:43:32 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0

Follow-up Comment #18, bug #58790 (project octave):

Yes, it is different to Octave 5.2.0:

GNU Octave Version: 7.0.0 (hg id: b9bf7a6bb8de)

Test 1.) An error is raised:
>> x=rand(30000000,10);
error: out of memory or dimension too large for Octave's index type

(IMHO the message is raised in pt-eval.cc)

Test 2.) Octave closes immediately instead of rejecting:
>> x=rand(20000000,10);
--> Octave closes immediately

Test 3.) Octave closes immediately instead of rejecting:
>> x=rand(10000000,10);
>> memory
Octave    RAM:    918916 kiB,  virt:   1829560 kiB
>> y=rand(10000000,10);
--> Octave closes immediately

The same tests in Octave 5.2.0 either result in correct rejection if there is
insufficient memory or an acceptance.

BTW, the win64 target also ends without an error message if too much memory is
allocated. However if one is careful and does the test on octave-cli w64, one
can read "LLVM ERROR: out of memory; fatal caught signal Aborted -- stoppfing
myself" immediately before the window closes.

I don't have a hg id near the RC around so i can't tell the situation there.


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]