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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blank screen on Mac after Dec Update #31

Open
tsny opened this issue Dec 13, 2021 · 3 comments
Open

Blank screen on Mac after Dec Update #31

tsny opened this issue Dec 13, 2021 · 3 comments

Comments

@tsny
Copy link

tsny commented Dec 13, 2021

Code version: November 2021 (version 1.63)

I get this error with code --verbose

[main 2021-12-13T03:49:36.354Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[65899:1212/214936.407085:INFO:CONSOLE(22)] "Uncaught (in promise) TypeError: Cannot convert undefined or null to object", source: vscode-file://vscode-app/Users/tasnyder/Library/Application%20Support/Code/User/globalStorage/iocave.monkey-patch/modules/browser-entrypoint.js (22)

Code ends up looking like this:
image

Deleting the files in that directory work but they re-appear and make the issue reappear after another restart.

Snippet from that file (starting at line 20):

		let joined = prevPattern.toString().slice(1, -1) + additionalPattern.toString().slice(1, -1);
		loaderConfig.amdModulesPattern = new RegExp(joined);
		Object.assign(loaderConfig.paths, {
			"customize-ui" : "../../../../../../Users/tasnyder/Library/Application Support/Code/User/globalStorage/iocave.customize-ui/modules",
			"monkey-generated" : "../../../../../../Users/tasnyder/Library/Application Support/Code/User/globalStorage/iocave.monkey-patch/modules"
		});
		require.define("monkey-patch", {
@knopp
Copy link
Collaborator

knopp commented Dec 13, 2021

Is line 22 Object.assign(loaderConfig.paths? If so it looks like loaderConfig.paths might be undefined, which is quite weird. Could you try editing the file, add

loaderConfig.paths = {}

right before Object.assign and let me know if VSCode starts?

@dtomasch
Copy link

dtomasch commented Feb 5, 2022

I'm having the same problem … MonkeyPatch was working fine until tonight when Code starts up as just a blank screen, same as OP. However, I don't get the error he had with code --verbose

I get —

[main 2022-02-05T04:04:45.586Z] [File Watcher (node.js)] Request to start watching: /Users/user/Library/Application Support/Code/User (excludes: ),/Users/user/Library/Application Support/Code/User/settings.json (excludes: )
[main 2022-02-05T04:04:45.592Z] Sending env to running instance...
[main 2022-02-05T04:04:45.596Z] [File Watcher (node.js)] Started watching: '/Users/user/Library/Application Support/Code/User'
[main 2022-02-05T04:04:45.597Z] [File Watcher (node.js)] Started watching: '/Users/user/Library/Application Support/Code/User/settings.json'
[main 2022-02-05T04:04:45.655Z] Sent env to running instance. Terminating...
[main 2022-02-05T04:04:45.655Z] Lifecycle#kill()
[main 2022-02-05T04:04:45.655Z] Lifecycle#onWillShutdown.fire()

Any thoughts?

@vanowm
Copy link

vanowm commented Aug 10, 2022

Running portable VSCode, same issue

Version: 1.70.0
Commit: da76f93349a72022ca4670c1b84860304616aaa2
Date: 2022-08-04T04:38:16.462Z
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: 10.0.139.17-electron.0
OS: Windows_NT x64 10.0.19044

Can anyone confirm this with non-portable version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants