Re: The need for perl_destruct()

2010/8/2 Reini Urban <rurban@x-ray.at>:
> I'm doing quite fine with breaking a new perl speed record.
> exit() is free'ing my malloc'ed memory just fine, and I'm doing no embedding.

Found a blocker:.
S_doeval frees of the temporary op root and so all its attached sv's.
That is the only case where a destruction is done in the middle of run-time.
DynaLoader::unload is rarely used.

> What else?
> Calling DESTROY hooks is the big remaining feature, which is really required.
> I'm thinking of a fast way to call all remaining DESTROY methods, but this
> should be it. Or did I miss something else?
>
> I don't care for freeing ops and svs, and esp. do not care for the
> long winding road finding all. And in the B::C compiler most of those
> are initialized static, so they don't need to be freed at all.
>
> Note that long-running server processes make no difference. They never
> reclaim memory,
> only at then end of the long-running process. So it will grow and
> grow, and "leaks" at the
> end will just be reclaimed by the OS.
> Just embedding is affected. I don't care for embedding.
-- 
Reini Urban

• The need for perl_destruct() by Reini Urban
• Re: The need for perl_destruct() by Reini Urban