A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.
Read the statement by Michael Teeuw here.
MESA issues - mm actually displays
-
Saw this error in
npm start
. Quick search says that these typically rnder a black screen - I am actually seeing MM, so what does this error mean?MESA-LOADER: failed to retrieve device information ../../buildtools/third_party/libc++/trunk/include/vector:1425: assertion __n < size() failed: vector[] index out of bounds[27159:1223/223830.134308:ERROR:gpu_process_host.cc(991)] GPU process exited unexpectedly: exit_code=6 MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to retrieve device information ../../buildtools/third_party/libc++/trunk/include/vector:1425: assertion __n < size() failed: vector[] index out of bounds[27202:1223/223831.357228:ERROR:command_buffer_proxy_impl.cc(128)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer. [27159:1223/223831.363276:ERROR:gpu_process_host.cc(991)] GPU process exited unexpectedly: exit_code=6 [27202:1223/223832.163432:ERROR:command_buffer_proxy_impl.cc(128)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
-
@nakulbende 90% of the time this can be ignored. If you’re getting your mirror up on screen, there’s no issue.
-
@nakulbende turn off use of the GPU.
add
export ELECTRON_DISABLE_GPU=1
to the place where you do
npm startadd that line before the npm start
in next release Jan 1,
we are doing this by default a d adding a new
ELECTRON_ENABLE_GPU=1as no one is really using the GPU