Message189245
| Author |
pitrou |
| Recipients |
amaury.forgeotdarc, benjamin.peterson, dabeaz, jsafrane, pitrou |
| Date |
2013年05月14日.18:45:13 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1368557111.2562.11.camel@fsol> |
| In-reply-to |
<51925809.2020104@redhat.com> |
| Content |
Le mardi 14 mai 2013 à 15:28 +0000, Jan Safranek a écrit :
> libpython2.7.so is not unloaded because python extensions, e.g.
> /usr/lib64/python2.7/lib-dynload/_heapq.so depend on it. And _heapq.so
> was dlopenened by Python and it was not dlclosed -> glibc does not
> unload it.
>
> It seems that Py_Finalize() does not even close opened shared objects.
> Isn't it a bug?
What do you call shared objects in this context? .so files?
Indeed they are not closed, because usually extension modules are not
reload-safe: therefore, their basic structures are kept eternally once
initialized. |
|