Doesn't work on latest vscode

[avionbg]

Windows 10 Extension Version: 0.4.5 VSCODE: Version: 1.32.3 (system setup) Commit: a3db5be9b5c6ba46bb7555ec5d60178ecc2eaae4 Date: 2019-03-14T23:43:35.476Z Electron: 3.1.6 Chrome: 66.0.3359.181 Node.js: 10.2.0 V8: 6.6.346.32 OS: Windows_NT x64 10.0.17134

Extension just doesn't work, its not opening any popup or at least it's not showing.

[anseki]

Hi @avionbg, thank you for your report. Could you give information? https://github.com/anseki/vscode-color/blob/master/.github/ISSUE_TEMPLATE.md Also, do you mean that the extension worked on previous version of VS Code?

[avionbg]

I already posted all the versions (vscode / extension / node etc.) that I'm using. If you need some other details just let me know exactly which one. Well unfortunately I didn't know about the extension before, so I cant say for sure if it works on earlier versions of vscode.

[anseki]

You did not write information about NPM and Log. See: https://github.com/anseki/vscode-color/blob/master/.github/ISSUE_TEMPLATE.md Please understand that those are important to solve an issue more than you think.

[avionbg]

System node/npm version:

node -v v10.15.1 npm -v 6.4.1

Steps to reproduce:

1. Install the extension from marketplace
2. Try to pick the color

Dev tools console log after reloading the window / clearing the log and enabling the extension:

[Extension Host] debugger listening on port 60694
log.ts:161  INFO no standard startup: not a new window
console.ts:134 [Extension Host] [vscode-icons] v8.4.0 activated!
console.ts:134 [Extension Host] Looking for parseable documents...
console.ts:134 [Extension Host] Found all parseable documents.
console.ts:134 [Extension Host] Parsing documents and looking for CSS class definitions...
console.ts:134 [Extension Host] Summary:
console.ts:134 [Extension Host]% 98 parseable documents found
console.ts:134 [Extension Host]% 665 CSS class definitions found
console.ts:134 [Extension Host]% 140 unique CSS class definitions found
console.ts:134 [Extension Host]% 4 failed attempts to parse. List of the documents:
console.ts:134 [Extension Host] /g:/DEV/ICS/aia-sow/src/css/theme.css
/g:/DEV/ICS/aia-sow/node_modules/prettier-stylelint/tests/error-syntax.css
/g:/DEV/ICS/aia-sow/node_modules/prettier-stylelint/tests/test-disable-rules.css
/g:/DEV/ICS/aia-sow/node_modules/postcss-discard-overridden/src/__tests__/fixtures/keyframes.css

3webviewElement.ts:284 [Embedded Page] Refused to apply inline style because it violates the following Content Security Policy directive: "style-src vscode-core-resource:". Either the 'unsafe-inline' keyword, a hash ('sha256-/hrnFLvlRLwUBJOsbTcaSST5mKtDLPuHe9GD9QefPS0='), or a nonce ('nonce-...') is required to enable inline execution.

log.ts:173   ERR Cannot assign to read only property 'user' of object '#<Object>': TypeError: Cannot assign to read only property 'user' of object '#<Object>'
    at c (file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:1479:114)
    at Object.t.getDefaultValues (file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:1481:319)
    at new d (file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:1491:834)
    at M.onDefaultConfigurationChanged (file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:4117:673)
    at M._register.S.Registry.as.onDidUpdateConfiguration.e (file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:4110:639)
    at d.fire (file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:73:416)
    at h.registerConfigurations (file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:1434:830)
    at g.m.setHandler [as _handler] (file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:2987:623)
    at g._handle (file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:2980:568)
    at g.acceptUsers (file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:2980:475)
    at Function._handleExtensionPoint (file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:3261:279)
    at e._rehandleExtensionPoints (file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:3251:583)
    at e.<anonymous> (file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:3250:905)
    at Generator.next (<anonymous>)
    at r (file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:30:772)

And this is the log when I execute the pick color command from the command palette:

[Extension Host] Start child process...
console.ts:134 [Extension Host] Check version of: electron-prebuilt
console.ts:134 [Extension Host] Check version of: comma-separated-values
console.ts:134 [Extension Host] Check version of: js-yaml
console.ts:134 [Extension Host] Check version of: process-bridge
console.ts:134 [Extension Host] Try to send IPC message: 3```

[anseki]

I see. Your GPU driver might have a problem. Specify 1 for colorHelper.disableGpu option.

[avionbg]

Yep .. that did the trick. What exactly might be the core problem with GPU driver ? (I'm using latest nvidia drivers and I haven't experienced any issue with it)

[anseki]

That option disables the GPU driver that has a problem. So, could you close this issue if it was solved?

[avionbg]

Yep, closing the issue..