Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Test-Simple CPAN distribution.

Report information
The Basics
Id: 74858
Status: rejected
Priority: 0/
Queue: Test-Simple
People
Owner: Nobody in particular
Requestors: RURBAN [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: Normal
Broken in: 0.98
Fixed in: (no value)

History Show all quoted text
  Fri Feb 10 13:16:34 2012 RURBAN [...] cpan.org - Ticket created
Subject: Test::More leaks with ithreads
This is really a CORE bug with threads, but I keep it here until we find the real cause. ribasushi found the leak in Devel::PeekPoke, I limited it down to Test::More. valgrind --leak-check=full /usr/local/bin/perl5.14.2d -MTest::More -e0 ==26633== LEAK SUMMARY: ==26633== definitely lost: 7,760 bytes in 182 blocks ==26633== indirectly lost: 726,750 bytes in 15,247 blocks The more tests, the more leaks. -Uuseithreads does not leak. Looks like some cloned OPs have the wrong refcnt or are not properly perl_destruct'ed. valgrind only reports OPs to leak. -- Reini Urban
  Fri Feb 10 14:55:46 2012 schwern [...] pobox.com - Correspondence added
Subject: Re: [rt.cpan.org #74858] Test::More leaks with ithreads
Date: Fri, 10 Feb 2012 11:55:29 -0800
To: bug-Test-Simple [...] rt.cpan.org
From: Michael G Schwern <schwern [...] pobox.com>
On 2012.2.10 10:16 AM, Reini Urban via RT wrote: Show quoted text
> This is really a CORE bug with threads, but I keep it here until we find > the real cause. > ribasushi found the leak in Devel::PeekPoke, I limited it down to > Test::More. > > valgrind --leak-check=full /usr/local/bin/perl5.14.2d -MTest::More -e0 > > ==26633== LEAK SUMMARY: > ==26633== definitely lost: 7,760 bytes in 182 blocks > ==26633== indirectly lost: 726,750 bytes in 15,247 blocks > > The more tests, the more leaks. > -Uuseithreads does not leak. > > Looks like some cloned OPs have the wrong refcnt or are not properly > perl_destruct'ed. valgrind only reports OPs to leak.
If I'm reading that right, there are leaks just loading Test::More on a threaded Perl? Not even running tests nor loading threads.pm?
  Fri Feb 10 14:55:47 2012 The RT System itself - Status changed from 'new' to 'open'
  Fri Feb 10 17:06:37 2012 rurban [...] x-ray.at - Correspondence added
CC: RURBAN [...] cpan.org
Subject: Re: [rt.cpan.org #74858] Test::More leaks with ithreads
Date: Fri, 10 Feb 2012 16:06:27 -0600
To: bug-Test-Simple [...] rt.cpan.org
From: Reini Urban <rurban [...] x-ray.at>
On Fri, Feb 10, 2012 at 1:55 PM, Michael G Schwern via RT <bug-Test-Simple@rt.cpan.org> wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=74858 > > > On 2012.2.10 10:16 AM, Reini Urban via RT wrote:
>> This is really a CORE bug with threads, but I keep it here until we find >> the real cause. >> ribasushi found the leak in Devel::PeekPoke, I limited it down to >> Test::More. >> >> valgrind --leak-check=full /usr/local/bin/perl5.14.2d -MTest::More -e0 >> >> ==26633== LEAK SUMMARY: >> ==26633==    definitely lost: 7,760 bytes in 182 blocks >> ==26633==    indirectly lost: 726,750 bytes in 15,247 blocks >> >> The more tests, the more leaks. >> -Uuseithreads does not leak. >> >> Looks like some cloned OPs have the wrong refcnt or are not properly >> perl_destruct'ed. valgrind only reports OPs to leak.
> > If I'm reading that right, there are leaks just loading Test::More on a > threaded Perl?  Not even running tests nor loading threads.pm?
right. The leaks are observable with -MTest::More -e0 but grow larger the more tests you run. This is really a bug for CORE, I just wanted to a ticket here also, and refer to it in the CORE perlbug. Should be easy to find with this info, but too hard for me. I'm not familiar with perl_clone. Something for Nick, Dave or Zefram. -- Reini Urban http://cpanel.net/   http://www.perl-compiler.org/
  Fri Oct 28 14:49:32 2016 exodist7 [...] gmail.com - Correspondence added
On Fri Feb 10 10:16:34 2012, RURBAN wrote: Show quoted text
> This is really a CORE bug with threads, but I keep it here until we find > the real cause. > ribasushi found the leak in Devel::PeekPoke, I limited it down to > Test::More. > > valgrind --leak-check=full /usr/local/bin/perl5.14.2d -MTest::More -e0 > > ==26633== LEAK SUMMARY: > ==26633== definitely lost: 7,760 bytes in 182 blocks > ==26633== indirectly lost: 726,750 bytes in 15,247 blocks > > The more tests, the more leaks. > -Uuseithreads does not leak. > > Looks like some cloned OPs have the wrong refcnt or are not properly > perl_destruct'ed. valgrind only reports OPs to leak.
Ticket is 4 years old, and not a problem for Test::More to fix, closing. If you really want a ticket against Test::More for this (and the problem continues on the latest version) please re-open on github.
  Fri Oct 28 14:49:33 2016 exodist7 [...] gmail.com - Status changed from 'open' to 'rejected'