Re: Memory Issues in Octave

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Memory Issues in Octave

Rik-4
Dmitri,

Why don't you file a bug report so you can attach these long logs.

Also, I built a version of Octave with the address sanitizer enabled and
then ran

run-octave -f --no-gui-libs --eval 'exit' | & tee leak.base.log
run-octave -f --no-gui-libs --eval 'graphics_toolkit gnuplot; plot (1:3);
exit' | & tee leak.gnuplot.log

The results were

SUMMARY: AddressSanitizer: 204896 byte(s) leaked in 3198 allocation(s).
SUMMARY: AddressSanitizer: 205184 byte(s) leaked in 3200 allocation(s).

So there does seem to be a problem.

--Rik

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Memory Issues in Octave

Dmitri A. Sergatskov
On Fri, Jul 21, 2017 at 11:48 AM, Rik <[hidden email]> wrote:
Dmitri,

Why don't you file a bug report so you can attach these long logs.

​I will.
 

Also, I built a version of Octave with the address sanitizer enabled and
then ran

run-octave -f --no-gui-libs --eval 'exit' | & tee leak.base.log
run-octave -f --no-gui-libs --eval 'graphics_toolkit gnuplot; plot (1:3);
exit' | & tee leak.gnuplot.log

The results were

SUMMARY: AddressSanitizer: 204896 byte(s) leaked in 3198 allocation(s).
SUMMARY: AddressSanitizer: 205184 byte(s) leaked in 3200 allocation(s).


​I have seen those as well. ​



 
So there does seem to be a problem.


​Some (most) of them are warnings, but some are errors which result in program
being aborted. E.g. i cannot really run "make check" since it dies on the very first test.​
​Many (most | all ?) of them comes with a
<<<
​HINT: this may be a false positive if your program uses some custom stack unwind mechanism or swapcontext
      (longjmp and C++ exceptions *are* supported)
>>>

​Any chance it could be the case?​
 
--Rik

​Dmitri.
--

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Memory Issues in Octave

Dmitri A. Sergatskov
In reply to this post by Rik-4


On Fri, Jul 21, 2017 at 11:48 AM, Rik <[hidden email]> wrote:
 

run-octave -f --no-gui-libs --eval 'exit' | & tee leak.base.log
run-octave -f --no-gui-libs --eval 'graphics_toolkit gnuplot; plot (1:3);
exit' | & tee leak.gnuplot.log

The results were

SUMMARY: AddressSanitizer: 204896 byte(s) leaked in 3198 allocation(s).
SUMMARY: AddressSanitizer: 205184 byte(s) leaked in 3200 allocation(s).


​most of those can be suppressed ​by setting ASAN_OPTIONS=leak_check_at_exit=0.
For some reason I cannot suppress "stack-use-after-scope" which seem to dominate.

--Rik

​Dmitri.
--

Loading...