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

Method over_release_count

nodedb-mem/src/budget.rs:174–176  ·  view source on GitHub ↗

Number of over-release events observed on this budget. A non-zero value is the smoking-gun signal that some call-site is releasing more bytes than it reserved. Per-engine `allocated()` saturates to zero on over-release, so this counter is the only post-hoc observable.

(&self)

Source from the content-addressed store, hash-verified

172 /// `allocated()` saturates to zero on over-release, so this
173 /// counter is the only post-hoc observable.
174 pub fn over_release_count(&self) -> usize {
175 self.over_release_count.load(Ordering::Relaxed)
176 }
177
178 /// Remaining bytes available.
179 pub fn available(&self) -> usize {

Callers 1

Calls 1

loadMethod · 0.45

Tested by

no test coverage detected