Message 276428 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	methane
Recipients	berker.peksag, methane, minrk, vstinner
Date	2016-09-14.12:57:15
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1473857835.5.0.989076537145.issue28147@psf.upfronthosting.co.za>
In-reply-to

Content
I don't understand the leak yet. > Each time dict_resize is called, it gets a new, larger size `> minused`. If this is triggered many times, it will keep growing in size by a factor of two each time, as the previous size is passed as minused for the next call. dictresize() is called for converting split table to combined table. How is it triggered many times? In your test code, which loop cause leak? new instance loop or re-use instance loop?

I don't understand the leak yet.

> Each time dict_resize is called, it gets a new, larger size `> minused`. If this is triggered many times, it will keep growing in size by a factor of two each time, as the previous size is passed as minused for the next call.

dictresize() is called for converting split table to combined table.
How is it triggered many times?

In your test code, which loop cause leak? new instance loop or re-use instance loop?

History
Date	User	Action	Args
2016-09-14 12:57:15	methane	set	recipients: + methane, vstinner, berker.peksag, minrk
2016-09-14 12:57:15	methane	set	messageid: <1473857835.5.0.989076537145.issue28147@psf.upfronthosting.co.za>
2016-09-14 12:57:15	methane	link	issue28147 messages
2016-09-14 12:57:15	methane	create