we've seen this on two computers this week (mac and windows). Not sure what I did to cause it in each case... but here's the traceback. There are some vispy issues out there that discuss this
➜ mmgui
WARNING: Error drawing visual <Image at 0x13f992930>
WARNING: Traceback (most recent call last):
File "/Users/talley/dev/self/pymmcore-gui/.venv/bin/mmgui", line 10, in <module>
sys.exit(main())
File "/Users/talley/dev/self/pymmcore-gui/src/pymmcore_gui/_app.py", line 113, in main
app.exec()
File "/Users/talley/dev/self/pymmcore-gui/.venv/lib/python3.12/site-packages/vispy/app/backends/_qt.py", line 626, in event
out = super(QtBaseCanvasBackend, self).event(ev)
File "/Users/talley/dev/self/pymmcore-gui/.venv/lib/python3.12/site-packages/vispy/app/backends/_qt.py", line 626, in event
out = super(QtBaseCanvasBackend, self).event(ev)
File "/Users/talley/dev/self/pymmcore-gui/.venv/lib/python3.12/site-packages/vispy/app/backends/_qt.py", line 928, in paintGL
self._vispy_canvas.events.draw(region=None)
File "/Users/talley/dev/self/pymmcore-gui/.venv/lib/python3.12/site-packages/vispy/util/event.py", line 453, in __call__
self._invoke_callback(cb, event)
File "/Users/talley/dev/self/pymmcore-gui/.venv/lib/python3.12/site-packages/vispy/util/event.py", line 471, in _invoke_callback
_handle_exception(self.ignore_callback_errors,
<< caught exception here: >>
File "/Users/talley/dev/self/pymmcore-gui/.venv/lib/python3.12/site-packages/vispy/util/event.py", line 469, in _invoke_callback
cb(event)
File "/Users/talley/dev/self/pymmcore-gui/.venv/lib/python3.12/site-packages/vispy/scene/canvas.py", line 219, in on_draw
self._draw_scene()
File "/Users/talley/dev/self/pymmcore-gui/.venv/lib/python3.12/site-packages/vispy/scene/canvas.py", line 278, in _draw_scene
self.draw_visual(self.scene)
File "/Users/talley/dev/self/pymmcore-gui/.venv/lib/python3.12/site-packages/vispy/scene/canvas.py", line 316, in draw_visual
node.draw()
File "/Users/talley/dev/self/pymmcore-gui/.venv/lib/python3.12/site-packages/vispy/scene/visuals.py", line 106, in draw
self._visual_superclass.draw(self)
File "/Users/talley/dev/self/pymmcore-gui/.venv/lib/python3.12/site-packages/vispy/visuals/visual.py", line 514, in draw
self._program.draw(self._vshare.draw_mode,
File "/Users/talley/dev/self/pymmcore-gui/.venv/lib/python3.12/site-packages/vispy/visuals/shaders/program.py", line 102, in draw
Program.draw(self, *args, **kwargs)
File "/Users/talley/dev/self/pymmcore-gui/.venv/lib/python3.12/site-packages/vispy/gloo/program.py", line 543, in draw
canvas.context.flush_commands()
File "/Users/talley/dev/self/pymmcore-gui/.venv/lib/python3.12/site-packages/vispy/gloo/context.py", line 172, in flush_commands
self.glir.flush(self.shared.parser)
File "/Users/talley/dev/self/pymmcore-gui/.venv/lib/python3.12/site-packages/vispy/gloo/glir.py", line 584, in flush
self._shared.flush(parser)
File "/Users/talley/dev/self/pymmcore-gui/.venv/lib/python3.12/site-packages/vispy/gloo/glir.py", line 506, in flush
parser.parse(self._filter(self.clear(), parser))
File "/Users/talley/dev/self/pymmcore-gui/.venv/lib/python3.12/site-packages/vispy/gloo/glir.py", line 824, in parse
self._parse(command)
File "/Users/talley/dev/self/pymmcore-gui/.venv/lib/python3.12/site-packages/vispy/gloo/glir.py", line 786, in _parse
ob.draw(*args)
File "/Users/talley/dev/self/pymmcore-gui/.venv/lib/python3.12/site-packages/vispy/gloo/glir.py", line 1333, in draw
gl.check_error('Check before draw')
File "/Users/talley/dev/self/pymmcore-gui/.venv/lib/python3.12/site-packages/vispy/gloo/gl/__init__.py", line 204, in check_error
raise err
RuntimeError: OpenGL got errors (Check before draw): GL_INVALID_VALUE
ERROR: Invoking <bound method SceneCanvas.on_draw of <SceneCanvas (PyQt6) at 0x13eabd310>> for DrawEvent
zsh: segmentation fault mmgui
we've seen this on two computers this week (mac and windows). Not sure what I did to cause it in each case... but here's the traceback. There are some vispy issues out there that discuss this