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 jsafrane
Recipients amaury.forgeotdarc, benjamin.peterson, dabeaz, jsafrane, pitrou
Date 2013-05-09.07:07:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <518B4B4A.5000109@redhat.com>
In-reply-to <1367940721.47.0.846910634765.issue17922@psf.upfronthosting.co.za>
Content
On 05/07/2013 05:32 PM, Antoine Pitrou wrote:
> Jan, one possibility would be for Pegasus to stop "unloading" Python,
> it seems.

It is always possibility. Actually, Pegasus "plugin" is just a shared
object (.so) and the .so is linked with Python. Pegasus calls dlopen()
and dlclose() on it. After dlclose(), the "plugin" is removed from
memory. Unfortunately, libpython2.7.so stays loaded, at least
/proc/XXX/mems says so. If there was a way to unload libpython2.7.so
from memory too...

Jan
History
Date User Action Args
2013-05-09 07:07:57jsafranesetrecipients: + jsafrane, amaury.forgeotdarc, pitrou, benjamin.peterson, dabeaz
2013-05-09 07:07:57jsafranelinkissue17922 messages
2013-05-09 07:07:57jsafranecreate