First time here? Check out the FAQ!

Wing Pro 9 freezes when debugging pygame-ce project

I'm using Wing Pro in Ubuntu 22.04.

My project uses pygame-ce (ce is community edition) with Python 3.10.12

When I put a breakpoint to debug my pygame project, Wing IDE freezes and then I must use htop to terminate the process and then restart Wing.

Wing will also freeze sometimes when my code raises an exception. I haven't had this issue with other libraries such as tkinter; I think this issue is specific to pygame. Any ideas?

jrez's avatar
asked 2023-08-05 11:51:39 -0500
Wingware Support's avatar
Wingware Support
updated 2023-12-07 08:23:05 -0500
edit flag offensive 0 remove flag close merge delete


I suspect something is going wrong with inspecting data in your code in order to display it in Wing's Stack Data or other debugger tools. Could you please send in a bug report from the Help menu after replicating the problem? That might show us what is failing. You could also try to set the Debugger > Diagnostics > Debug Internals Log File preference and sending us that output (but without the extremely verbose option).

Wingware Support's avatar Wingware Support (2023-08-07 08:52:00 -0500) edit
add a comment see more comments

1 Answer


Based on emailed details, this is probably an XGrabPointer or similar locking up the entire Linux UI and not being released when a break point or exception is reached. There are some possible solutions listed here:…

Wingware Support's avatar
Wingware Support
answered 2023-08-07 09:20:22 -0500
edit flag offensive 0 remove flag delete link


Thanks, I plan on switching to Debian 12 soon (which I believe uses Wayland), so that might be a solution for me (apparently the MATE desktop, which is what I use, doesn't support Wayland).

jrez's avatar jrez (2023-08-07 09:45:14 -0500) edit

In the short-term you may also just be able to move where you put a break point, or rework code a little. In Wing, we had this a lot for code that was actually doing a menu item's action during the menu selection time, when the XGrab was still in place. By instead scheduling an action that happens after the UI menu action is completed (and XGrab is released) the problem largely went away. This may or may not be useful, though, depending on your code.

Wingware Support's avatar Wingware Support (2023-08-07 11:47:32 -0500) edit
add a comment see more comments

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss.

Add Answer