You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
cppia: report what keeps a released module loaded #264
After release(), a module's code is freed once nothing reaches it, and __scriptable_cppia_live_modules() counts the modules not freed yet (docs/CppiaModuleRelease.md). When a released module stays loaded, nothing says why, so finding the listener, closure or static that still holds it means guessing.
A call that collects and then reports, for each released module still loaded:
the live instances of its classes, by class, with counts and bytes;
closures and bound methods of its functions still held;
where practical, what holds them: a host static, a root registered from native code, a thread's stack.
It could work in release builds like __hxcpp_gc_census (#82), which already tallies live objects by class during a collection; attributing script classes to their module would cover the first point.
Moving this past 6.0.0. It is a diagnostic, not a defect, and the first point can build on the census from #82 now that it is on main: attributing script classes to their module would give the per-module counts.
Activity
dimensionscape commentedon Oct 22, 2026
Moving this past 6.0.0. It is a diagnostic, not a defect, and the first point can build on the census from #82 now that it is on main: attributing script classes to their module would give the per-module counts.
Report what keeps a released cppia module loaded