A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2014-April/134257.html below:

[Python-Dev] ref leaks

[Python-Dev] ref leaksEthan Furman ethan at stoneleaf.us
Thu Apr 24 16:31:22 CEST 2014
On 04/23/2014 09:06 PM, Benjamin Peterson wrote:
> On Wed, Apr 23, 2014, at 19:14, Ethan Furman wrote:
>> Command line:
>>
>>     ./python -m test.regrtest -v -R3:3 test_tools
>>
>> Results:
>>
>>     Ran 44 tests in 7.628s
>>
>>     OK (skipped=1)
>>     .
>>     test_tools leaked [0, 2, 2] references, sum=4
>>     1 test failed:
>>         test_tools
>>
>> Any words of wisdom for tracking those leaks?
>
> Unless it's consistent, that sort of behavior usually just gets
> dismissed as intermittent.

test_tools leaked [331, 0, 0] references, sum=331
test_tools leaked [108, 1, 0] memory blocks, sum=109

test_tools leaked [2, 0, 0] references, sum=2

test_tools leaked [0, 0, 4] references, sum=4
test_tools leaked [0, 0, 3] memory blocks, sum=3

Consistently the same, or consistently happening?  ;)

--
~Ethan~
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4