[Octave-bug-tracker] [bug #52061] Memory issue whenever Java JVM is used

[Dmitri A. Sergatskov]

Follow-up Comment #16, bug #52061 (project octave):

Here is another one:


 ASAN_OPTIONS="leak_check_at_exit=0"
LD_PRELOAD="libasan.so.4:libGLX_mesa.so.0" ./run-octave -g --no-gui
=================================================================
==21065==ERROR: AddressSanitizer: alloc-dealloc-mismatch (malloc vs operator
delete) on 0x613000000040
    #0 0x7f52480d3fd0 in operator delete(void*) (/lib64/libasan.so.4+0xe0fd0)
    #1 0x55c2bec41c62  (/usr/libexec/gdb+0x1bcc62)
    #2 0x55c2beeda20e  (/usr/libexec/gdb+0x45520e)
    #3 0x55c2beeaca64  (/usr/libexec/gdb+0x427a64)
    #4 0x55c2bee22d4f  (/usr/libexec/gdb+0x39dd4f)
    #5 0x55c2beb9072a  (/usr/libexec/gdb+0x10b72a)
    #6 0x7f52448f3509 in __libc_start_main (/lib64/libc.so.6+0x20509)
    #7 0x55c2beb92859  (/usr/libexec/gdb+0x10d859)

0x613000000040 is located 0 bytes inside of 334-byte region
[0x613000000040,0x61300000018e)
allocated by thread T0 here:
    #0 0x7f52480d1850 in malloc (/lib64/libasan.so.4+0xde850)
    #1 0x55c2bee32240 in operator new(unsigned long)
(/usr/libexec/gdb+0x3ad240)

SUMMARY: AddressSanitizer: alloc-dealloc-mismatch
(/lib64/libasan.so.4+0xe0fd0) in operator delete(void*)
==21065==HINT: if you don't care about these errors you may set
ASAN_OPTIONS=alloc_dealloc_mismatch=0
==21065==ABORTING


So i cannot start gdb. it is all looks false positive to me so far. But I will
keep an eye on it.

Dmitri.
-- 





    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?52061>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/