Under the hood
Useful2 Signal2
Long-lived caches now clear per session or fork rather than lasting the whole process.
What's wrong with this entry?
Anonymous. No account, no email.
What
Dozens of long-lived caches now hang off a session state object with a reset method, so they can be cleared per session or fork instead of living for the whole process.
Details
- Covers the install-latest in-flight promise, task-list leader name, artifact live, auto-react and wake registries, clipboard probe results, gitignore pattern compile caches, the plugin activity ring buffer, marketplace tip caches, the plugin flag cache, session title and agent-name events, and the background-result-seen channel.
Evidence
resetMarketplaceCaches
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.235
Process-wide caches are now scoped per host
Both mention state
-
v2.1.235
Per-session state replaces process-wide globals, and the render root takes explicit dependencies
Both mention state
-
v2.1.235
More file-scope variables replaced by accessor-backed containers
Both mention state