MCPcopy Create free account
hub / github.com/NodeDB-Lab/nodedb / total_over_release_count

Method total_over_release_count

nodedb-mem/src/governor.rs:407–409  ·  view source on GitHub ↗

Total number of over-release events observed across all per-engine budgets. A non-zero value signals at least one call-site is releasing more bytes than it reserved — the "memory release exceeds allocation" warning class. Per-engine `allocated()` saturates to zero on over-release, so this counter is the only post-hoc observable for the bug.

(&self)

Source from the content-addressed store, hash-verified

405 /// `allocated()` saturates to zero on over-release, so this
406 /// counter is the only post-hoc observable for the bug.
407 pub fn total_over_release_count(&self) -> usize {
408 self.budgets.values().map(|b| b.over_release_count()).sum()
409 }
410
411 /// Global utilization as a percentage (0-100). Computed in `u128` so a
412 /// corrupted engine-layer sum clamps to 100 % instead of overflowing.

Calls 2

sumMethod · 0.80
over_release_countMethod · 0.80