Change:
// Actions const buttons = mainItem.buttons; if (buttons && buttons.length) { <del> data.actionBar.push(buttons.map((button, index): IAction => { let cssClasses = button.iconClass || (button.iconPath ? getIconClass(button.iconPath) : undefined); if (button.alwaysVisible) { cssClasses = cssClasses ? `${cssClasses} always-visible` : 'always-visible'; } return { id: `id-${index}`, class: cssClasses, enabled: true, label: '', tooltip: button.tooltip || '', run: () => { mainItem.type !== 'separator' ? element.fireButtonTriggered({ button, item: mainItem }) : element.fireSeparatorButtonTriggered({ button, separator: mainItem }); } }; }), { icon: true, label: false }); </del> <ins> data.actionBar.push(buttons.map((button, index) => quickInputButtonToAction( button, `id-${index}`, () => mainItem.type !== 'separator' ? element.fireButtonTriggered({ button, item: mainItem }) : element.fireSeparatorButtonTriggered({ button, separator: mainItem }) )), { icon: true, label: false }); </ins> data.entry.classList.add('has-actions'); } else { data.entry.classList.remove('has-actions');

Discussion:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.85.1 OS Version: Ubuntu 23.04 Steps to Reproduce: the command palette using ctrl+shift+p (or cmd+shift+p on mac) the escape key, closing the command palette 7 times that instance count has increased by 7, instance count has increased by 211, instance count has increased by 240 and instance count has increased by 302. The total disposable count has increased by 1137 from to . One class that has increased the most in the above test was . Looking where relates to the quick input I found this code in where actions are created: Perhaps it could be this code that causes the to be created. It seems the actions aren't registered/disposed like other disposables.
Thanks for reporting this! I think I've cleaned up the ... now we use the simpler non-disposable kind... I'll chip away at the rest over time.
Thanks a lot, I see now: No more Actions are leaked (211 -0) Disposable stores are 211 less leaked (240 -29) Emitter are 211 less leaked (302 -91) MutableDisposable instance count still increases (7 -7) I'll try to find more information for the MutableDisposables and DisposableStores where exactly they are created! Thanks again! Edit: The MutableDisposables are created in : They are kept alive by a 200ms timeout and disposed after 200ms so it's no problem: Just the test executing too fast / finishing before the MutableDisposables were disposed. :)