2 people reported
All time, since Oct 8.
Cache entries pin buffer slabs
“Each renders at request time and calls a 'use cache' function keyed by the segment (about 1.5 KB per entry).”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/next-js/issues/7326/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Small 'use cache' entries pin whole Buffer pool slabs in memory. The default handler buffers values with Buffer.concat, so retained ArrayBuffers far exceed the cacheMaxMemorySize the LRU counts.
Is this your bug?
File my report- Where
- use cache handler
- Versions
- 16.4.0 to 16.4.1
- Platforms
- macOS
- How bad
- Breaks a normal workflow.
Original reports3, newest first
- Default 'use cache' handler keeps a 64 KB buffer-pool slab alive per small entry, so cacheMaxMemorySize undercounts memoryOn GitHub#100492
- Default 'use cache' handler keeps a 64 KB buffer-pool slab alive per small entry, so cacheMaxMemorySize undercounts memoryOn GitHub#100491
- Default "use cache" handler: small entries pin whole Buffer pool slabs, so memory far exceeds cacheMaxMemorySize (Node 26: 22x)On GitHub#99848