[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: luacom paralyzes os.exit
- From: Artur Galyamov <artur-pub@...>
- Date: Wed, 03 Mar 2010 18:27:21 +0300
03.03.10, 09:33, "Roberto Ierusalimschy" <roberto@inf.puc-rio.br>:
> > So far it does the job but I'm not sure if there is any memory
> > leakage. The manual says it will free all memory associated with the
> > state but does it include those locked in COM and OLE? In comparison,
> > the php manual explicitly says that an exit() will free all memory and
> > object destructors will always be executed. [...]
>
> I am not sure what you are saying, but the Lua manual also states that
> lua_close will execute all object destructors:
>
> http://www.lua.org/manual/5.1/manual.html#lua_close
I think php manual says "we maintain list of all created interpreter states (both
active and closed) and carefully kill them atexit(3)" in reader-friendly way...
--
Artur