Crash Linux X BadWindow (EGL/fluxbox X11/AMD)
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
People
(Reporter: zlice555, Unassigned)
Details
(Keywords: crash, nightly-community, regression)
Attachments
(1 file)
(deleted),
text/plain
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:98.0) Gecko/20100101 Firefox/98.0
Steps to reproduce:
Browse the web, sometimes a new window, other times just sitting on a page that must still be loading.
This happened once I updated to nightly 98.
Actual results:
Silent crashes, have only been able to get this one time while running from a terminal.
(firefox:5387): Gdk-WARNING **: 13:25:38.217: The program 'firefox' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 101448 error_code 3 request_code 129 (SHAPE) minor_code 2)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Expected results:
No random crashes, or at least a error dialogue window to send to FF.
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Comment 2•3 years ago
|
||
Thanks for the report! Please open about:support, click on "Copy text to clipboard" and paste it here.
Comment 4•3 years ago
|
||
Thanks! Which desktop environment and distribution are you using?
void linux, fluxbox + rox. not really standard, latest libs and what not
Comment 6•3 years ago
|
||
Are you able to find a regression range? You get a pushlog URL at the end.
$ pip3 install --user --upgrade mozregression
$ ~/.local/bin/mozregression --good 97 --bad 98 -a https://example.org
I'm not sure when/if I'll have time since it seems random. But I'm confident it wasn't happening until I updated to nightly 98.
I'll try to update if it starts happening again today.
Updated•3 years ago
|
Updated•3 years ago
|
Have had this happen today. Also some other (idk if related) crashes trying to navigate bookmarks, but those sent reports.
Comment 9•3 years ago
|
||
I'm getting a similar error after updating firefox-developer-edition
from 97.0b2-1
to 97.0b3-1
on Arch Linux:
(firefoxdeveloperedition:18458): Gdk-WARNING **: 13:46:04.401: The program 'firefoxdeveloperedition' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 109237 error_code 3 request_code 129 (SHAPE) minor_code 2)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Comment 10•3 years ago
|
||
(In reply to Benoit Pierre from comment #9)
I'm getting a similar error after updating
firefox-developer-edition
from97.0b2-1
to97.0b3-1
on Arch Linux:
Thanks! bug 1750017 comment 0 found the same regressing bug.
Comment 11•3 years ago
|
||
(In reply to Benoit Pierre from comment #9)
Which desktop environment are you using?
Comment 12•3 years ago
|
||
System information:
Operating System: Arch Linux (64 bit)
Kernel Version: 5.16.0-arch1
X Server Release: 12101003
X Window Manager: awesome
Video Card: Intel Open Source Technology Center Mesa DRI Intel(R) HD Graphics 4000 (IVB GT2)
Driver Version: 3.0 Mesa 21.3.4
I can confirm that I can reproduce the issue by attempting to move a tab to another window (although that's not what I was doing the 2 times Firefox crashed before).
Is there still a need for running mozregression
?
Comment 13•3 years ago
|
||
(In reply to Benoit Pierre from comment #12)
Thanks!
Is there still a need for running
mozregression
?
No, bug 1750017 comment 0 has the precise regression range.
Description
•