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)
| 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. |