This was caused by a stack-use-after-free due to passing a lambda directly into a `FunctionRef` that keeps a reference to it. This only happened for me in an asan build, but not in a release/debug build.
This was caused by a stack-use-after-free due to passing a lambda directly into a `FunctionRef` that keeps a reference to it. This only happened for me in an asan build, but not in a release/debug build.