[Tarantool-patches] [PATCH] lua: prohibit fiber yield when GC hook is active
Kirill Yukhin
kyukhin at tarantool.org
Tue Oct 6 13:56:17 MSK 2020
Hello,
On 02 окт 17:39, Igor Munkin wrote:
> While running GC hook (i.e. __gc metamethod) garbage collector engine
> is "stopped": the memory penalty threshold is set to LJ_MAX_MEM and
> incremental GC step is not triggered as a result. Ergo, yielding the
> execution at the finalizer body leads to further running platform with
> disabled LuaJIT GC. It is not re-enabled until the yielded fiber doesn't
> get the execution back.
>
> This changeset extends <cord_on_yield> routine with the check whether GC
> hook is active. If the switch-over occurs in scope of __gc metamethod
> the platform is forced to stop its execution with EXIT_FAILURE and calls
> panic routine before the exit.
>
> Relates to #4518
> Follows up #4727
>
> Signed-off-by: Igor Munkin <imun at tarantool.org>
I've checked your patch into 1.10, 2.4, 2.5 and master.
--
Regards, Kirill Yukhin
More information about the Tarantool-patches
mailing list