Re: Memory leaks in Octave

[Rik]

On 09/19/2017 11:07 AM, Rik wrote:

On 09/19/2017 10:22 AM, Rik wrote:

On 09/18/2017 09:00 AM, address@hidden wrote:

Subject:

Re: Memory leaks in Octave

From:

"Dmitri A. Sergatskov" <address@hidden>

Date:

09/18/2017 05:34 AM

To:

siko1056 <address@hidden>

CC:

octave-maintainers <address@hidden>

List-Post:

<mailto:address@hidden>

Precedence:

list

MIME-Version:

1.0

References:

<address@hidden> <address@hidden> <address@hidden> <address@hidden>

In-Reply-To:

<address@hidden>

Message-ID:

<address@hidden>

Content-Type:

multipart/alternative; boundary="94eb2c1c13a40efb89055975f53f"

Message:

2

On Fri, Sep 15, 2017 at 7:55 AM, siko1056 <address@hidden> wrote:

Rik-4 wrote
>
> Dmitri A. Sergatskov wrote
>> ​My builds with gcc7.1.1 and ASAN pretty much fail
> I'm building with gcc-5.4.0 and I don't see this.

My experience using "gcc-7 (SUSE Linux) 7.1.1 20170607" was also bad.  Lots
of linking errors, when the oct-files were created.  But using "gcc (SUSE
Linux) 4.8.5" works for me.  The first issue "make check" detected is QT5
related:

 libinterp/octave-value/ov-class.cc-tst ......................ASAN:SIGSEGV
=================================================================
==4516== ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc
0x7fae70a6e2b4 sp 0x7faec2abf398 bp 0x7fae8aa78820 T10)
AddressSanitizer can not provide additional info.
    #0 0x7fae70a6e2b3 (+0x2b3)
Thread T10 (QThread) created by T0 here:
    #0 0x7faefcdf213b (/usr/lib64/libasan.so.0.0.0+0xb13b)
    #1 0x7faef8890fd5 (/usr/lib64/libQt5Core.so.5.6.2+0xaefd5)
==4516== ABORTING

Did I trapped into inappropriate threading options?

​I recompiled with-qt and get  ​the same problem

(It passes when compiled without-qt without-fltk)

I am now experiencing this too.  Since I wasn't getting this when I first explored using the Address Sanitizer, it implies that something has changed in just the last few weeks.  I will try and bisect.

On my system configuring with --disable-java stops this from happening.  I didn't need to use --without-qt and --without-fltk.  If you can verify the same then a new bug report should be filed about that.

--Rik

Dmitri,

I filed a new bug report about Java and memory leaks (https://savannah.gnu.org/bugs/index.php?52061).  It turns out that any usage of the JVM seems to cause a segfault.

--Rik