500 Error
complete
B
Bryan Hoyt
complete
Closing this ticket now -- thanks for your help and all the info along the way! To help folks identify this kind of issue more easily in future, we've added a more specific / helpful error message.
z
zmpeterson86nwes
This is now working on Edge, but not on Chrome
z
zmpeterson86nwes
I am no longer able to access projects anymore. I have WebGL enabled, but now I get the 500 error again. This happens on all projects.
B
Bryan Hoyt
zmpeterson86nwes: very sorry to hear that! Unfortunately I can't see what's happening on this end to isolate the problem, but could you please help me be opening the Chrome dev console (by pressing Ctrl+Shift+J or Option+⌘+J on MacOS) and telling me what appears in there when you load a project?
Ideally, if you could share me a screenshot or loom.com screencast, that would be extremely helpful.
z
zmpeterson86nwes
Bryan Hoyt: Here is a video I gave to Nicolas. I am still seeing the same behavior.
Console output:
instrument.js:107 THREE.WebGLRenderer: Error creating WebGL context.
(anonymous) @ instrument.js:107
(anonymous) @ captureconsole.js:73
ke @ three.module.js:26269
createWebGLRenderer @ SceneManager.ts:279
E @ SceneManager.ts:162
Bt @ ThreeEntryPoint.tsx:81
(anonymous) @ SchematicEditor.tsx:122
ol @ react-dom.production.min.js:242
xn @ react-dom.production.min.js:285
ea @ react-dom.production.min.js:272
Ct @ react-dom.production.min.js:127
qf @ react-dom.production.min.js:282
Kt @ react-dom.production.min.js:280
bs @ react-dom.production.min.js:268
Ne @ scheduler.production.min.js:13
Ft @ scheduler.production.min.js:14
n @ setImmediate.js:40
t @ setImmediate.js:69
x @ setImmediate.js:109
postMessage (async)
u @ setImmediate.js:120
e @ setImmediate.js:27
ut @ scheduler.production.min.js:14
Ft @ scheduler.production.min.js:14
n @ setImmediate.js:40
t @ setImmediate.js:69
x @ setImmediate.js:109
postMessage (async)
u @ setImmediate.js:120
e @ setImmediate.js:27
ut @ scheduler.production.min.js:14
Ft @ scheduler.production.min.js:14
n @ setImmediate.js:40
t @ setImmediate.js:69
x @ setImmediate.js:109
postMessage (async)
u @ setImmediate.js:120
e @ setImmediate.js:27
ut @ scheduler.production.min.js:14
Ft @ scheduler.production.min.js:14
n @ setImmediate.js:40
t @ setImmediate.js:69
x @ setImmediate.js:109
postMessage (async)
u @ setImmediate.js:120
e @ setImmediate.js:27
ut @ scheduler.production.min.js:14
Ft @ scheduler.production.min.js:14
n @ setImmediate.js:40
t @ setImmediate.js:69
x @ setImmediate.js:109
postMessage (async)
u @ setImmediate.js:120
e @ setImmediate.js:27
ut @ scheduler.production.min.js:14
Ft @ scheduler.production.min.js:14
n @ setImmediate.js:40
t @ setImmediate.js:69
x @ setImmediate.js:109
postMessage (async)
u @ setImmediate.js:120
e @ setImmediate.js:27
ut @ scheduler.production.min.js:14
Ft @ scheduler.production.min.js:14
n @ setImmediate.js:40
t @ setImmediate.js:69
x @ setImmediate.js:109
postMessage (async)
u @ setImmediate.js:120
e @ setImmediate.js:27
ut @ scheduler.production.min.js:14
Re @ scheduler.production.min.js:14
L.unstable_scheduleCallback @ scheduler.production.min.js:18
sa @ react-dom.production.min.js:297
Ee @ react-dom.production.min.js:266
ia @ react-dom.production.min.js:287
tc @ react-dom.production.min.js:288
Promise.then (async)
(anonymous) @ react-dom.production.min.js:249
Ks @ react-dom.production.min.js:249
Ys @ react-dom.production.min.js:254
Je @ react-dom.production.min.js:250
Ys @ react-dom.production.min.js:256
Je @ react-dom.production.min.js:250
Ys @ react-dom.production.min.js:256
Je @ react-dom.production.min.js:250
Ys @ react-dom.production.min.js:251
Je @ react-dom.production.min.js:250
Ys @ react-dom.production.min.js:256
Je @ react-dom.production.min.js:250
Ys @ react-dom.production.min.js:251
Je @ react-dom.production.min.js:250
Ys @ react-dom.production.min.js:251
Je @ react-dom.production.min.js:250
Ys @ react-dom.production.min.js:256
Je @ react-dom.production.min.js:250
Ys @ react-dom.production.min.js:251
Je @ react-dom.production.min.js:250
Ys @ react-dom.production.min.js:256
Je @ react-dom.production.min.js:250
Ys @ react-dom.production.min.js:251
Je @ react-dom.production.min.js:250
Ys @ react-dom.production.min.js:256
Je @ react-dom.production.min.js:250
Ys @ react-dom.production.min.js:256
Je @ react-dom.production.min.js:250
Ys @ react-dom.production.min.js:251
Je @ react-dom.production.min.js:250
Ys @ react-dom.production.min.js:253
qf @ react-dom.production.min.js:282
Kt @ react-dom.production.min.js:280
ea @ react-dom.production.min.js:272
Ct @ react-dom.production.min.js:127
(anonymous) @ react-dom.production.min.js:266
instrument.js:107 Error: Error creating WebGL context.
at new ke (three.module.js:26247:12)
at E.createWebGLRenderer (SceneManager.ts:279:26)
at new E (SceneManager.ts:162:43)
at Bt (ThreeEntryPoint.tsx:81:26)
at SchematicEditor.tsx:122:34
at ol (react-dom.production.min.js:242:332)
at xn (react-dom.production.min.js:285:111)
at ea (react-dom.production.min.js:272:185)
at Ct (react-dom.production.min.js:127:105)
at qf (react-dom.production.min.js:282:419)
at Kt (react-dom.production.min.js:280:398)
at bs (react-dom.production.min.js:268:459)
at Ne (scheduler.production.min.js:13:203)
at Ft (scheduler.production.min.js:14:128)
at n (setImmediate.js:40:13)
at t (setImmediate.js:69:21)
at x (setImmediate.js:109:17)
B
Bryan Hoyt
zmpeterson86nwes: thanks for that. Strangely, it looks like much the same error you were getting before the upgrade and before it temporarily started working again. I'm struggling to pinpoint the cause of this. Could you help me by giving me some information on your system, to help uncover whether there's something we're missing:
* Version of Chrome
* Operating system and version
* Graphics card and driver version, if you are able to find this (here are some ways to do this on Windows: https://www.avast.com/c-check-graphics-card)
* Make / model of your computer
Thanks!
z
zmpeterson86nwes
Bryan Hoyt: Now it's working on chrome again.
Chrome version:
106.0.5249.103 (Official Build) (64-bit) (cohort: Rampup_106)
OS: Windows 10 Home
Graphics: Intel Iris Xe, version 27.20.100.9039
B
Bryan Hoyt
zmpeterson86nwes: thanks for the info. Since it's intermittent, it's hard to know what this issue could be. However, a couple ideas to move forward if it happens again:
- One common potential cause is low memory / low system resources. Flux does currently consume a fair amount of memory and CPU (which we're working on improving). If you get this again, try closing extra tabs and programs to see if that helps.
- If it does happen again, we would be very interested in seeing the results you get from pointing your browser at https://webglreport.com/
z
zmpeterson86nwes
Bryan Hoyt: Ok thanks for the info, I will try this when there is a problem and I will keep in touch
Matthias
zmpeterson86nwes: the graphics drivers are quite old
there is a much newer version available...maybe try that?
z
zmpeterson86nwes
Matthias: I updated and it loads okay now, I'll follow up if it's still a problem
Greg Dingle
in progress
z
zmpeterson86nwes
I am now able to access projects, I enabled WebGL and updated Chrome