Extension not loading
See original GitHub issueHey there! thanks for building this!
I’m having an issue with the latest version of the extension (1.1.4) and VSCode (1.56.2) where the extension will not load. I’ve attached the log below. Happy to provide anything else if it helps you debug further.
[2021-06-09 20:36:14.502] [exthost] [info] ExtensionService#_doActivateExtension leodevbro.blockman {"startup":false,"extensionId":{"value":"leodevbro.blockman","_lower":"leodevbro.blockman"},"activationEvent":"onStartupFinished"}
[2021-06-09 20:36:14.502] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/lachlanheywood/.vscode/extensions/leodevbro.blockman-1.1.4/out/extension.js
[2021-06-09 20:36:15.085] [exthost] [error] Activating extension leodevbro.blockman failed due to an error:
[2021-06-09 20:36:15.085] [exthost] [error] Error: Cannot invoke loadWASM more than once.
at Object.t.loadWASM (/Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar/vscode-oniguruma/release/main.js:1:4823)
at TextMateLoader.loadOniguruma (/Users/~~/.vscode/extensions/leodevbro.blockman-1.1.4/out/bracketAlgos/textMateLoader.js:122:19)
at new TextMateLoader (/Users/~~/.vscode/extensions/leodevbro.blockman-1.1.4/out/bracketAlgos/textMateLoader.js:21:31)
at new Settings (/Users/~~/.vscode/extensions/leodevbro.blockman-1.1.4/out/bracketAlgos/settings.js:10:31)
at new DocumentDecorationManager (/Users/~~/.vscode/extensions/leodevbro.blockman-1.1.4/out/bracketAlgos/documentDecorationManager.js:10:25)
at activate (/Users/~~/.vscode/extensions/leodevbro.blockman-1.1.4/out/extension.js:747:30)
at Function._callActivateOptional (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:92:14813)
at Function._callActivate (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:92:14486)
at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:92:12643
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async Promise.all (index 0)
It also shows an error when I attempt the ‘Toggle Enable/Disable’ command. Not sure if this is related, or if it is a result of the extension failing to load, but here’s that error also:
Command 'Blockman Toggle Enable/Disable' resulted in an error (command 'blockman.toggleEnableDisable' not found)
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:10 (6 by maintainers)
Top Results From Across the Web
7 Solutions for Chrome Extension Not Working [2022 Updated]
Why is Chrome Extension Not Working? · Solution #1: Force Restart · Solution #2: Clear Cache · Solution #3: Remove Some Extensions ·...
Read more >Fix problems with apps, extensions, or themes - Chrome Web ...
Open the Chrome Web Store. · At the top right, click Settings and then My Extensions & Apps. · Click the app, extension,...
Read more >Chrome Extension is Not Working - Copper Help Center
Chrome Extension is Not Working · Option 1: Clear your cache · Option 2: Try Reinstalling our Extension · Option 3: Disable other...
Read more >Top 7 Ways to Fix Google Chrome Failed to Load Extension
Top 7 Ways to Fix Google Chrome Failed to Load Extension · 1. Restart Google Chrome · 2. Update Extension · 3. Reinstall...
Read more >Fix: Chrome Extensions Stopped Working - Appuals.com
What is causing the Chrome Extensions to stop working? · Glitched Google Chrome process · Installed Extensions Conflict · Outdated Chrome or ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Confirmed that updating to latest version of VSCode (1.57.0) solves this problem. Thanks, @leodevbro!
Also, let’s move back to this new issue: https://github.com/leodevbro/vscode-blockman/issues/93
Because your problem seems different.