pyglet: Catalina Mac OS segfaulting in pyglet.input
Hi, I’m moving this over from: https://github.com/pvcraven/arcade/issues/513
I have a number of students using Arcade this semester, which is built on Pyglet. It’s working well for most of my students, but some of the Macs with Catalina (15.5) segfault before Arcade can finish importing. I believe at this point, I’ve tracked it down to running the following:
import pyglet.input
This causes a segmentation fault and a large dump. I don’t have the exact trace for that command (student I was working with had to go to their next class), but here’s the stack trace from when I was still at the Arcade level: https://pastebin.com/raw/6NyDtJmC
Not sure if you have any insight, but my first thought is that it has something to do with the game controllers?
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 21 (16 by maintainers)
Commits related to this issue
- Troubleshooting #95 — committed to pyglet/pyglet by benmoran56 5 years ago
- Add additional try/except to test workaround for issue #95 — committed to pyglet/pyglet by benmoran56 4 years ago
- Checking for NULL pointer as a workaround for #95 — committed to volgy/pyglet by volgy 4 years ago
- Checking for NULL pointer as a workaround for #95 (#119) Thank you! — committed to pyglet/pyglet by volgy 4 years ago
The try/except block does not catch a (low-level) segmentation fault. Just checking for a null pointer is probably the best workaround (see PR #119).