ShootOFF icon indicating copy to clipboard operation
ShootOFF copied to clipboard

glGetError 0x505 on Raspberry Pi

Open phrack opened this issue 8 years ago • 3 comments

glGetError 0x505 java.lang.NullPointerException at com.sun.prism.impl.BaseGraphics.drawTexture(BaseGraphics.java:411) at com.sun.prism.impl.ps.BaseShaderGraphics.drawTexture(BaseShaderGraphics.java:139) at com.sun.javafx.sg.prism.NGImageView.renderContent(NGImageView.java:123) at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2056) at com.sun.javafx.sg.prism.NGImageView.doRender(NGImageView.java:103) at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1948) at com.sun.javafx.sg.prism.NGGroup.renderContent(NGGroup.java:235) at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2056) at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1948) at com.sun.javafx.sg.prism.NGGroup.renderContent(NGGroup.java:235) at com.sun.javafx.sg.prism.NGRegion.renderContent(NGRegion.java:576) at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2056) at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1948) at com.sun.javafx.sg.prism.NGGroup.renderContent(NGGroup.java:235) at com.sun.javafx.sg.prism.NGRegion.renderContent(NGRegion.java:576) at com.sun.javafx.sg.prism.NGNode.renderForClip(NGNode.java:2297) at com.sun.javafx.sg.prism.NGNode.renderRectClip(NGNode.java:2191) at com.sun.javafx.sg.prism.NGNode.renderClip(NGNode.java:2217) at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2050) at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1948) at com.sun.javafx.sg.prism.NGGroup.renderContent(NGGroup.java:235) at com.sun.javafx.sg.prism.NGRegion.renderContent(NGRegion.java:576) at com.sun.javafx.sg.prism.NGNode.renderForClip(NGNode.java:2297) at com.sun.javafx.sg.prism.NGNode.renderRectClip(NGNode.java:2191) at com.sun.javafx.sg.prism.NGNode.renderClip(NGNode.java:2217) at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2050) at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1948) at com.sun.javafx.sg.prism.NGGroup.renderContent(NGGroup.java:235) at com.sun.javafx.sg.prism.NGRegion.renderContent(NGRegion.java:576) at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2056) at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1948) at com.sun.javafx.sg.prism.NGGroup.renderContent(NGGroup.java:235) at com.sun.javafx.sg.prism.NGRegion.renderContent(NGRegion.java:576) at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2056) at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1948) at com.sun.javafx.sg.prism.NGGroup.renderContent(NGGroup.java:235) at com.sun.javafx.sg.prism.NGRegion.renderContent(NGRegion.java:576) at com.sun.javafx.sg.prism.NGNode.doRender(NGNode.java:2056) at com.sun.javafx.sg.prism.NGNode.render(NGNode.java:1948) at com.sun.javafx.tk.quantum.ViewPainter.doPaint(ViewPainter.java:477) at com.sun.javafx.tk.quantum.ViewPainter.paintImpl(ViewPainter.java:323) at com.sun.javafx.tk.quantum.PresentingPainter.run(PresentingPainter.java:91) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at com.sun.javafx.tk.RenderJob.run(RenderJob.java:58) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(QuantumRenderer.java:125) at java.lang.Thread.run(Thread.java:745)

phrack avatar Mar 04 '17 18:03 phrack

@cbdmaul I'll leave this here, but removed it from a milestone. This is a video memory issue we can maybe solve with OS configuration in Raspbian. If we can't find a sweet spot this may be the thing that moves us off the Pi.

To be more specific, this is due to a lack of video memory. We can only get more by stealing available RAM for it, meaning we have less RAM for the OS and ShootOFF's backend.

phrack avatar Mar 25 '17 17:03 phrack

Is anything else using video memory while ShootOFF is running? X?

cbdmaul avatar Mar 30 '17 01:03 cbdmaul

LXDE is too. I'll have to measure this. It's entirely possible JavaFX is just greedy with memory and will bloat into a small space quickly.

phrack avatar Mar 30 '17 11:03 phrack