Segfault when using specific Keyboard

[RoedyAdraxe]

Dear PyGui version:

2.3.1

Python version:

3.14.6, python 3.11.5

Operating system:

Macos 26.5.1 (25F80)

My issue/question:

This was a very interesting troubleshooting process with the help of an AI assistant.

Keyboard: Keychron K10 HE
Transport: USB

MacOSCrashLog.txt

Vendor ID: 0x3434 (13364)
Product ID: 0x0EA0
Firmware/Product Version: 0x0111

Environment:

• macOS 26.5.1
• Apple Silicon (M5 Pro)
• Python 3.12.13 ARM64
• DearPyGui 2.3.1

Behavior:

• DearPyGui crashes when opening a viewport with the keyboard connected via USB.
• DearPyGui works normally if:
  • the keyboard is disconnected, or
  • the same keyboard is connected via RF receiver.

MacOS crash log is included as an attachment

Steps to reproduce:

Plug a Keychron HE10 keyboard into the computer over USB. There is an onboard switch to choose the transport type as USB

Run the dearpygui demo

python -m dearpygui.demo

Expected behavior:

I would expect the keyboard to work over USB or any other transport

Screenshots:

N/A

Standalone, minimal, complete and verifiable example:

python -m dearpygui.demo

[v-ein]

OMG this might be the most weird DPG issue of all times! 😂

The issue in fact lies deep within GLFW, a backend library that DPG uses on macOS. DPG uses GLFW version 3.3.7, and the issue has probably been fixed in 3.4, but I don't have a rock solid proof yet. Unfortunately we can't just flick a switch and get GLFW 3.4 into DPG - this update needs to be done carefully and is therefore not on our plans yet.

Let's keep the ticket open as a reminder that we now have a reason to update GLFW in DPG.

[RoedyAdraxe]

Haha, yeah debugging this was pretty interesting. Imagine my surprise after a few hours when I realized it was my keyboard causing the segfaults 😆

Totally understand that this takes time so no worries, I know how to work around it! Thanks for maintaining this awesome gui framework.