Reproduced on Windows 10 with all add-ons disabled (held Shift during launch).
Anki 26.05 (e64c6b1a)
Python 3.13.13 Qt 6.11.0 Chromium 140
Platform: Windows 10
Steps: clicked the “Decks” button 20 times, then measured the main Anki
process, and repeated. PowerShell:
Get-Process | Where-Object {$.Name -match 'anki'} |
Select-Object Name, Id, HandleCount,
@{n='PrivateMB';e={[math]::Round($.PrivateMemorySize64/1MB)}}
Results (each row remeasured after +20 deck browser renders):
HandleCount PrivateMB
2729 640 (baseline, on anki launch)
2874 1072
3018 1459
3160 1757
3287 2047
3415 2359
3549 2650
3676 2952
3817 3241
3942 3557
4085 3940
4215 4240
4338 4579
4471 4956
4610 5306
4773 5647
4905 6030
5036 6367
5174 6703
5324 7043
Roughly +130 handles and +330 MB per 20 clicks increasing linearly
(~6.5 handles / ~16 MB leaked per deck browser render).
After 5 minutes idle: 5315 handles / 7031 MB, no recovery at all.
The deck browser clicking is just the easiest way to reproduce and measure
it. The same growth happens during normal reviewing (my cards have audio +
images, memory rises steadily as I answer cards, sometimes 100+ MB at once).
In practice a normal review session climbs to 7+ GB and eventually OOMs the
machine. Restarting Anki fully resets it.
Happy to run any further diagnostics.