Closed Recon419A closed 5 years ago
It seems to be caused by compatibility between GPU and Chromium. (e.g. Similar case of Ubuntu Chromium)
If you are ready to build Marp from source, could you try to add app.disableHardwareAcceleration()
to coffee/main.coffee:49
? As below:
app.on 'ready', ->
app.disableHardwareAcceleration()
global.marp.mainMenu = new MainMenu
...
We would have worth to support to disable GPU acceleration if this issue would improved in above.
Sorry to take so long getting back.
When I made that change, I got different behavior. npm start
produced a popup with the following error:
A JavaScript error occurred in the main process
Uncaught Exception:
Error: app.disableHardwareAcceleration() can only be called before app is ready
at Error (native)
at EventEmitter.<anonymous> (/home/drew/apps/marp/js/main.js:1:1161)
at emitOne (events.js:101:20)
at EventEmitter.emit (events.js:188:7)
It looks like it doesn't want me to call it there.
The stack trace tells you to move it before app.on 'ready'
. Look for where app is defined and move the line there to see if that helps. Maybe try around line 13 of main.coffee?
When I run the program (both from 0.0.8 and building from source), I get a black screen. Unfortunately, I'm having issues with screen shots right now as well, so I can't paste it, but the terminal does print like a thousand of these:
[electron] [7373:0812/112208:ERROR:gles2_cmd_decoder.cc(2167)] [.CommandBufferContext.RenderWorker-0x16244b262140]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command