?????? LuaJIT GC Problem
- From: "klince" <klince@xxxxxx>
- To: "luajit" <luajit@xxxxxxxxxxxxx>
- Date: Thu, 18 Oct 2018 10:32:23 +0800
adding `jit.flush()` is an overreaction. even more telling people to
do that without the back history; -- Javier
There are only two solutions, one is to add a code-unrelated simple line
before a work-independent code, the other is to teach everyone in project
to write code carefully to avoid a memory leaking that may happen. I don't
know what you would choose but I have to give consideration to noob
programmers in my team.
I might find some of the leaking code, but I can never spend time finding
them again and again. You know, the key problem is, the code seems quite
correctly. I'm not even aware of anything wrong by using upvalue that way.
In fact, I think I am right. I really don't like the solution of changing an
upvalue to a param of the function, if so, what's the point of upvalue?
--
klince
Other related posts:
