Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assertion Failed: argument is undefined or null: Error: Assertion Failed: argument is undefined or null #105734

Closed
isidorn opened this issue Aug 31, 2020 · 1 comment
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders verified Verification succeeded
Milestone

Comments

@isidorn
Copy link
Contributor

isidorn commented Aug 31, 2020

  1. VS Code, open debug console in the panel
  2. Reload window
  3. Exception in the debug console 馃悰

The Debug Console is not present on startup, it gets registered lazily. And due to that it can not be opened on reload.
Thus I think the current behavior of opening the terminal is perfectly fine, but throwing in the dev console we should not do.

Stack trace

  ERR Assertion Failed: argument is undefined or null: Error: Assertion Failed: argument is undefined or null
    at Object.assertIsDefined (file:///Users/isidor/Development/vscode/out/vs/base/common/types.js:93:19)
    at PanelPart.createComposite (file:///Users/isidor/Development/vscode/out/vs/workbench/browser/parts/compositePart.js:89:149)
    at PanelPart.doOpenComposite (file:///Users/isidor/Development/vscode/out/vs/workbench/browser/parts/compositePart.js:56:36)
    at PanelPart.openComposite (file:///Users/isidor/Development/vscode/out/vs/workbench/browser/parts/compositePart.js:43:25)
    at PanelPart.doOpenPanel (file:///Users/isidor/Development/vscode/out/vs/workbench/browser/parts/panel/panelPart.js:334:25)
    at PanelPart.openPanel (file:///Users/isidor/Development/vscode/out/vs/workbench/browser/parts/panel/panelPart.js:338:29)
    at Object.openComposite (file:///Users/isidor/Development/vscode/out/vs/workbench/browser/parts/panel/panelPart.js:41:54)
    at CompositeBar.resetActiveComposite (file:///Users/isidor/Development/vscode/out/vs/workbench/browser/parts/compositeBar.js:299:30)
    at CompositeBar.hideComposite (file:///Users/isidor/Development/vscode/out/vs/workbench/browser/parts/compositeBar.js:239:22)
    at PanelPart.hideComposite (file:///Users/isidor/Development/vscode/out/vs/workbench/browser/parts/panel/panelPart.js:227:31)
    at PanelPart.onDidChangeActiveViews (file:///Users/isidor/Development/vscode/out/vs/workbench/browser/parts/panel/panelPart.js:184:22)
    at PanelPart.onDidRegisterPanels (file:///Users/isidor/Development/vscode/out/vs/workbench/browser/parts/panel/panelPart.js:133:22)
    at file:///Users/isidor/Development/vscode/out/vs/workbench/browser/parts/panel/panelPart.js:198:70
    at Emitter.fire (file:///Users/isidor/Development/vscode/out/vs/base/common/event.js:456:38)
    at PanelRegistry.registerComposite (file:///Users/isidor/Development/vscode/out/vs/workbench/browser/composite.js:203:33)
    at PanelRegistry.registerPanel (file:///Users/isidor/Development/vscode/out/vs/workbench/browser/panel.js:29:19)
    at ViewsService.registerPanel (file:///Users/isidor/Development/vscode/out/vs/workbench/browser/parts/views/viewsService.js:382:63)
    at ViewsService.registerViewletOrPanel (file:///Users/isidor/Development/vscode/out/vs/workbench/browser/parts/views/viewsService.js:341:26)
    at ViewsService.onDidRegisterViewContainer (file:///Users/isidor/Development/vscode/out/vs/workbench/browser/parts/views/viewsService.js:93:18)
    at file:///Users/isidor/Development/vscode/out/vs/workbench/browser/parts/views/viewsService.js:37:85
    at Array.forEach (<anonymous>)
    at new ViewsService (file:///Users/isidor/Development/vscode/out/vs/workbench/browser/parts/views/viewsService.js:37:55)
    at InstantiationService._createInstance (file:///Users/isidor/Development/vscode/out/vs/platform/instantiation/common/instantiationService.js:88:20)
    at InstantiationService._createServiceInstance (file:///Users/isidor/Development/vscode/out/vs/platform/instantiation/common/instantiationService.js:177:29)
    at InstantiationService._createServiceInstanceWithOwner (file:///Users/isidor/Development/vscode/out/vs/platform/instantiation/common/instantiationService.js:165:29)
    at InstantiationService._createAndCacheServiceInstance (file:///Users/isidor/Development/vscode/out/vs/platform/instantiation/common/instantiationService.js:156:43)
    at InstantiationService._getOrCreateServiceInstance (file:///Users/isidor/Development/vscode/out/vs/platform/instantiation/common/instantiationService.js:113:29)
    at Object.get (file:///Users/isidor/Development/vscode/out/vs/platform/instantiation/common/instantiationService.js:36:45)
    at Workbench.initLayout (file:///Users/isidor/Development/vscode/out/vs/workbench/browser/layout.js:146:42)
    at file:///Users/isidor/Development/vscode/out/vs/workbench/browser/workbench.js:67:26
    at InstantiationService.invokeFunction (file:///Users/isidor/Development/vscode/out/vs/platform/instantiation/common/instantiationService.js:43:24)
    at Workbench.startup (file:///Users/isidor/Development/vscode/out/vs/workbench/browser/workbench.js:61:38)
    at DesktopMain.open (file:///Users/isidor/Development/vscode/out/vs/workbench/electron-browser/desktop.main.js:62:52)
@sbatten
Copy link
Member

sbatten commented Sep 3, 2020

The repro only works if the debug console is not in its original container. test by right clicking the title and notice reset location.

@isidorn @sandy081 it seems the viewsservice changes at some point made registering the panels happen too soon for the panel part to be ready. I don't really see a logical way to avoid this so instead of preventing registration, i prevent opening the composite and let the composite part figure out the active container when it is created. pls verify this is sane

@sbatten sbatten added this to the August 2020 milestone Sep 4, 2020
@sbatten sbatten added the bug Issue identified by VS Code Team member as probable bug label Sep 4, 2020
@RMacfarlane RMacfarlane added the verified Verification succeeded label Sep 4, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Oct 18, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

4 participants
@isidorn @RMacfarlane @sbatten and others