yklua doesn't use yk_location_drop() at all at the moment, so locations are leaked.
This would be less of a concern if we only leaked locations created statically by the parser, but the Lua interpreter has this tendency to dynamically dump/undump functions (bypassing the parser entirely). During dumping we lose references to locations, and during undumping we create fresh locations, which in turn go on to leak.
Depending on the program being executed, this dump+undump can happen quite a bit.
A side-question I don't know the answer to is: what happens if you drop a location that the JIT is using (e.g. tracing, compiling, ...).
yklua doesn't use
yk_location_drop()at all at the moment, so locations are leaked.This would be less of a concern if we only leaked locations created statically by the parser, but the Lua interpreter has this tendency to dynamically dump/undump functions (bypassing the parser entirely). During dumping we lose references to locations, and during undumping we create fresh locations, which in turn go on to leak.
Depending on the program being executed, this dump+undump can happen quite a bit.
A side-question I don't know the answer to is: what happens if you drop a location that the JIT is using (e.g. tracing, compiling, ...).