Re: How to best solve fragmentation issues

["Alex Davies" <alex.mania@...>]

Altough in any case, lua_close will have freed all memory. Unless you are 
using malloc elsewhere, or something. But Lua itself won't leak any ;). 
Might want to check your log tool? Or enable lua_assert, on lua_close it 
will assert that bytes allocated = 0 (for your piece of mind).

- Alex

----- Original Message ----- 
From: "Asko Kauppi" <askok@dnainternet.net>
To: "Lua list" <lua@bazar2.conectiva.com.br>
Sent: Tuesday, February 26, 2008 1:44 AM
Subject: Re: How to best solve fragmentation issues


> Did you run the collect cycle _twice_, when trying it?
>
> See the Lua reference, part of the releases only happen after the  second 
> gc call.