pez has already seen this, but for any one else interested, the following link gave a walk-through of profiling vscode extensions: https://www.nicoespeon.com/en/2019/11/fix-vscode-extension-performance-issue/ it worked for extensions written using cljs as well -- though telling apart anonymous functions ended up being some work.