ERR Failed to execute 'invoke' on 'CreateURLCallback':

[jrieken]

• use built-in debugger
• run the "VS Code" launch config
• often, not always see the error below

ERR Failed to execute 'invoke' on 'CreateURLCallback': The provided callback is no longer runnable.: Error: Failed to execute 'invoke' on 'CreateURLCallback': The provided callback is no longer runnable.
    at BrowserScriptLoader.load (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/loader.js:682:52)
    at OnlyOnceScriptLoader.load (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/loader.js:618:32)
    at loadNextPath (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/loader.js:1677:41)
    at ModuleManager._loadModule (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/loader.js:1689:13)
    at ModuleManager._resolve (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/loader.js:1774:26)
    at ModuleManager.defineModule (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/loader.js:1421:18)
    at ModuleManager._relativeRequire (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/loader.js:1455:18)
    at result (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/loader.js:1629:30)
    at vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/workbench/services/textMate/browser/abstractTextMateService.js:171:113
    at new Promise (<anonymous>)
    at TextMateService._getOrCreateGrammarFactory (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/workbench/services/textMate/browser/abstractTextMateService.js:171:74)
    at Object.createTokenizationSupport (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/workbench/services/textMate/browser/abstractTextMateService.js:200:59)
    at TokenizationSupportFactoryData._create (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/editor/common/tokenizationRegistry.js:117:63)
    at TokenizationSupportFactoryData.resolve (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/editor/common/tokenizationRegistry.js:112:45)
    at TokenizationRegistry.getOrCreate (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/editor/common/tokenizationRegistry.js:58:27)
    at ExtensionPoint._handler (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/workbench/services/textMate/browser/abstractTextMateService.js:120:54)
    at ExtensionPoint._handle (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/workbench/services/extensions/common/extensionsRegistry.js:87:22)
    at ExtensionPoint.acceptUsers (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/workbench/services/extensions/common/extensionsRegistry.js:80:18)
    at AbstractExtensionService._handleExtensionPoint (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/workbench/services/extensions/common/abstractExtensionService.js:1041:28)
    at SandboxExtensionService._doHandleExtensionPoints (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/workbench/services/extensions/common/abstractExtensionService.js:992:46)
    at SandboxExtensionService._startLocalExtensionHost (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/workbench/services/extensions/electron-sandbox/electronExtensionService.js:444:18)
    at async SandboxExtensionService._scanAndHandleExtensions (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/workbench/services/extensions/electron-sandbox/electronExtensionService.js:412:13)
    at async SandboxExtensionService._initialize (vscode-file://vscode-app/Users/jrieken/Code/vscode/out/vs/workbench/services/extensions/common/abstractExtensionService.js:613:17)

[jrieken]

It looks like the trusted types factoring for creating urls is somehow becoming invalid. I only see this when debugging and not in when running VS Code for real. This recovers after a renderer reload

[alexdima]

@jrieken The stack points to this line which came in with the trusted types work in the loader. I'm happy to help with loader problems as best I can but this seems to be a problem of combining trusted types and debugging. Maybe we need to disable trusted types when debugging?

[connor4312]

There seem to be assorted issues in Chromium regarding that error, and a few more that are closed. There is one open issue that evaluating trusted types while the debugger is paused fails, but that doesn't seem to be what you're encountering here. I don't like the idea of turning off trusted types while debugging, since that makes it easy to create something that only breaks 'in production'.

Do you notice any pattern to this happening that we could potentially use to inform a Chromium bug report?

[jrieken]

since that makes it easy to create something that only breaks 'in production'.

I don't think that's a good idea because it will simply delay fatal failures which we should spot early on.

The stack points to this line which came in with the trusted types work in the loader. I'm happy to help with loader problems as best I can but this seems to be a problem of combining trusted types and debugging

I know where this coming from but I also know that this was working for the longest time and only became an issue recently (roughly six weeks ago). So, I wonder if was caused by

• debugger changes?
• electron changes?
• changes that we made for bundling main/CJS resources?

[alexdima]

Chromium issue search turned up 1131368, could that be the root problem?

[vscodenpa]

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding, and happy coding!