Bug #108739 for Text-Bidi: Possible memory leak when running t/ucd.t

Wed Nov 11 09:14:20 2015 ppisar [...] redhat.com - Ticket created

Subject:

Possible memory leak when running t/ucd.t

Running t/ucd.t consumes a lot of memory. It looks like a memory leak. By the way, when regenerating the private.c by SWIG 3.0.7, I get this warning: /usr/bin/swig -perl -Wall -I/usr/include -I/usr/include/fribidi -outdir lib/Text/Bidi/ -o private.c swig/fribidi.i /usr/include/fribidi/fribidi-unicode.h:55: Warning 451: Setting a const char * variable may leak memory. swig/fribidi.i:253: Warning 451: Setting a const char * variable may leak memory. I have freebidi 0.19.7.

Fri Nov 13 00:57:30 2015 kamensky [...] cpan.org - Correspondence added

On Wed Nov 11 09:14:20 2015, ppisar wrote: Show quoted text

> Running t/ucd.t consumes a lot of memory. It looks like a memory leak. > > By the way, when regenerating the private.c by SWIG 3.0.7, I get this > warning: > > /usr/bin/swig -perl -Wall -I/usr/include -I/usr/include/fribidi > -outdir lib/Text/Bidi/ -o private.c swig/fribidi.i > /usr/include/fribidi/fribidi-unicode.h:55: Warning 451: Setting a > const char * variable may leak memory. > swig/fribidi.i:253: Warning 451: Setting a const char * variable may > leak memory. > > I have freebidi 0.19.7.

Thanks for reporting. I will try to look at it when I can, though I don't really know how to debug these things. I think the warning is irrelevant (at any rate, it was there from the beginning).

Fri Nov 13 00:57:30 2015 The RT System itself - Status changed from 'new' to 'open'

Fri Nov 13 00:57:31 2015 kamensky [...] cpan.org - Taken

Thu Dec 03 15:22:13 2015 SREZIC [...] cpan.org - Correspondence added

On 2015-11-11 09:14:20, ppisar wrote: Show quoted text

> Running t/ucd.t consumes a lot of memory. It looks like a memory leak.

On some machines the test suite fails because of this problem. Example report with a segfault: http://www.cpantesters.org/cpan/report/9ec3959a-865a-11e5-bdf8-ca90e0bfc7aa

Sat Jan 21 13:22:21 2017 SREZIC [...] cpan.org - Broken in 2.12 added

Wed Sep 26 02:04:43 2018 SREZIC [...] cpan.org - Broken in 2.15 added

Sun Feb 16 13:22:05 2020 SREZIC [...] cpan.org - Correspondence added

On 2015-12-03 15:22:13, SREZIC wrote: Show quoted text

> On 2015-11-11 09:14:20, ppisar wrote:

> > Running t/ucd.t consumes a lot of memory. It looks like a memory > > leak.

> > On some machines the test suite fails because of this problem. Example > report with a segfault: > http://www.cpantesters.org/cpan/report/9ec3959a-865a-11e5-bdf8- > ca90e0bfc7aa

I wonder whether the problem is caused by too many test cases. ucd.t has more than 450000 test cases, which is quite much. Maybe the situation would be better if instead of Test::More::is() a normal perl-level equality check is done, and only in case of a failure a Test::More::fail() is issued.