Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERROR: Unhandled XServer error: BadWindow (invalid Window parameter) #102633

Closed
jdsutton7 opened this issue Feb 9, 2025 · 8 comments
Closed

ERROR: Unhandled XServer error: BadWindow (invalid Window parameter) #102633

jdsutton7 opened this issue Feb 9, 2025 · 8 comments

Comments

@jdsutton7
Copy link

jdsutton7 commented Feb 9, 2025

Tested versions

4.4.beta1.mono.official d33da79

System information

Godot v4.4.beta1.mono - Linux Mint 22.1 (Xia) on X11 - X11 display driver, Multi-window, 1 monitor - OpenGL 3 (Compatibility) - NVIDIA GeForce GTX 1070 (nvidia; 550.120) - Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (8 threads)

Issue description

Godot frequently crashes with the following error:

ERROR: Unhandled XServer error: BadWindow (invalid Window parameter)
   Major opcode of failed request: 20
   Serial number of failed request: 0
   Current serial number in output stream: 938799
   at: default_window_error_handler (platform/linuxbsd/x11/display_server_x11.cpp:1180)

Steps to reproduce

Edit any project and run the game - happens intermittently

Minimal reproduction project (MRP)

N/A - happens across projects

@matheusmdx
Copy link
Contributor

This looks like the same problem as #102321 that was fixed by #102329. Could you test the 4.4 beta 3 and see if was fixed?

@Talavanor
Copy link

I had this issue crop up running on Godot v4.4.beta3. So far it happened a single time and I've been unable to find any sort of repro for it.

System information

Godot v4.4.beta3 - EndeavourOS #1 SMP PREEMPT_DYNAMIC Sun, 02 Feb 2025 01:02:29 +0000 on Wayland - X11 display driver, Multi-window, 2 monitors - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3070 (nvidia; 570.86.16) - Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz (12 threads)

@matheusmdx
Copy link
Contributor

@Talavanor Check issue #102321, there has the steps to reproduce the bug and a video that shows the steps.

@Talavanor
Copy link

Talavanor commented Feb 18, 2025

Alright, ran through those repro steps in #102321 and as many variations on them I could think of, but I've been unable to get it to happen again after a few hours of work. I will keep an eye out for the error cropping up again and try to get better info if it does.

@jdsutton7
Copy link
Author

jdsutton7 commented Feb 19, 2025 via email

@matheusmdx
Copy link
Contributor

I'll close this as fixed by #102329. If you find this bug again in 4.4 beta 3 or up let us know so the issue can be reopened.

@matheusmdx matheusmdx added this to the 4.4 milestone Feb 19, 2025
@gelvinp
Copy link
Contributor

gelvinp commented Mar 11, 2025

I am encountering this on 4.4-stable, though I'm not even interacting with the Godot window, and nothing is crashing.

For background, I'm trying to verify which commit introduced the xcb "unknown sequence number" issue, so I have two instances of Godot open. One of them is from 4.4-stable, and the other has a few small changes applied on top of that. Mostly I'm just leaving them open on a side monitor for the next 24 hours to make sure that the one I expect to crash is crashing, and the one I expect to not crash is not.

For each version, I have both the editor open (with update continuously not checked) and a "game" running from the editor (with low processor mode enabled). The game is a Node3D with a camera and nothing else, and a tool script that counts how many hours the game and editor have been running.

I've had a few "Unhandled XServer error: BadWindow (invalid Window parameter)" errors pop up on the modified version, usually they appear at the same time that I'm closing a different program (i.e. I exit firefox, and that moment is when one of the errors appeared). I thought this was a strange side effect of the change I was testing, but I just saw it happen on the unmodified 4.4-stable build as well. I can reliably cause the error by just opening the KDE plasma application launcher (see screen recording).

2025-03-10.17-20-18.mp4

Nothing has hung or crashed, both editors and game windows are still open, and the timer scripts are continuing to print out to the console each hour.

@matheusmdx
Copy link
Contributor

@gelvinp Could you create a new issue? As you have the same error but don't crash like this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants