Message411323
| Author |
gvanrossum |
| Recipients |
Mark.Shannon, eric.snow, gvanrossum, vstinner |
| Date |
2022年01月23日.00:59:43 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1642899584.04.0.70665780238.issue46476@roundup.psfhosted.org> |
| In-reply-to |
| Content |
If any of the immortal, deep-frozen code objects is ever quickened, I suppose the quickening data is never freed. But when we finalize and reinitialize, the co_quickened flag should remain set, so this would be a one-time leak.
The question is whether the quickening cache points to any objects that *are* freed. If it does, that could be bad. If it doesn't, then all we lose is a fixed amount of memory (no further leaks if we finalize and initialize the runtime repeatedly).
However, if my theory holds, why would valgrind consider the memory leaked? (TBH I don't know what valgrind does, so maybe that's not the right question.) |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2022年01月23日 00:59:44 | gvanrossum | set | recipients:
+ gvanrossum, vstinner, Mark.Shannon, eric.snow |
| 2022年01月23日 00:59:44 | gvanrossum | set | messageid: <1642899584.04.0.70665780238.issue46476@roundup.psfhosted.org> |
| 2022年01月23日 00:59:44 | gvanrossum | link | issue46476 messages |
| 2022年01月23日 00:59:43 | gvanrossum | create |
|