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
cache: t4 keeps a tombstone for every removed key #92
Found by a memory-accounting audit of 8b3c813. The tests are on branch audit/memory-tests and fail on main today; check out that branch to run them. File and line links point at that commit.
What goes wrong. t4 0.1.9 keeps an in-memory tombstone for every key ever removed until the store is remounted. Its index therefore grows with the number of distinct keys ever spilled, not with live ones. The root cause is in t4, as with #63, but the cost lands here.
Evidence.
At a steady population of about 1,350 live entries, heap grew 80.5 bytes per key ever spilled (release build, or debug with the trace drained), with no plateau.
The t4 store alone, with no cache, grew 82.1 bytes per removed key.
Flags: P probabilistic (a pass after a fix only means the race wasn't hit), F interleaving forced by a test hook, L Linux only, D needs Docker, M measurement only, C control (passes by design).
Activity