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 gregory.p.smith
Recipients carljm, corona10, dino.viehland, eelizondo, gregory.p.smith, nascheme, pablogsal, pitrou, shihai1991, steve.dower, tim.peters, vstinner
Date 2020-04-14.18:09:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Marking everything as immortal/eternal after you've loaded your common code & data but before you do your forking is thenorm for this kind of serving system.

You already presumably have a defined lifetime for the processes so they'll likely be set to die within N hours or days.  Memory leaks of too many things persisting is a non-issue in this kind of system.

The alternative of trying to pick and choose exactly what (and anything they reference) sticks around is a maintenance nightmare exercise in futility.
Date User Action Args
2020-04-14 18:09:20gregory.p.smithsetrecipients: + gregory.p.smith, tim.peters, nascheme, pitrou, vstinner, carljm, dino.viehland, steve.dower, corona10, pablogsal, eelizondo, shihai1991
2020-04-14 18:09:20gregory.p.smithsetmessageid: <>
2020-04-14 18:09:20gregory.p.smithlinkissue40255 messages
2020-04-14 18:09:20gregory.p.smithcreate