Non-catchable OOM in hot paths
- From: Egor Skriptunoff <egor.skriptunoff@xxxxxxxxx>
- To: luajit@xxxxxxxxxxxxx
- Date: Wed, 3 Feb 2021 15:42:42 +0300
Previously, in 2020, the "Current status" page of LuaJIT 2.1 documentation
(doc/status.html) contained the following text:
Currently some out-of-memory errors from on-trace code are not handled
correctly. The error may fall through an on-trace pcall or it may be passed
on to the function set with lua_atpanic on x64. This issue will be fixed
with the new garbage collector.
It seems LuaJIT does already have a new stable GC64.
Is the problem already solved?
It is strange that as of now the "Current status" page in LuaJIT 2.1 docs
has the OOM-errors paragraph still present, but its last sentence "This
issue will be fixed" has disappeared.
Was fixing removed from the future plans?
Or is it just a mistake in the documentation?
Other related posts:
