-
-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
[BUG] X Error: GLXBadDrawable, Major opcode: 151, Minor opcode: 26, Serial: 23995 #2645
Comments
Provide the full log and a gdb backtrace of the crash. |
Here's the full log: 2020-04-04 17-22-14.txt. How do I get a gdb backtrace of the crash? EDIT Is this it?
|
I cant replicate this also using 4k canvas. You would need to backtrace from the first error in order to diagnose further. |
Not sure if this is the same bug but it might be related. Opening filters for a video source and then closing the filters window resulted in a crash semi consistently.
|
Hi, this is CompuCat from the TASBot team; while hosting the TASGiving 2020 charity event, we experienced crashes matching this description consistently, causing OBS to hard-crash numerous times during a marathon stream. We still managed to raise $10,000 USD for NAMI, but we need to isolate the cause of this crash to avoid it for next year's marathon. Specifically, closing a filter window would semi-consistently trigger the crash. I don't have physical access to the stream system right now, but as soon as I can SSH back in we should be able to grab crash logs. System was running Linux Mint (LMDE 4 IIRC) on a Threadripper 2950X/NVIDIA RTX 2070; OBS was compiled from Git master as of ~1 week before Thanksgiving. (Will edit this comment to include exact commit hash.) Issue was consistently reproduced with both NVENC and x264 encoders. |
Was just on a lucky streak. |
xcompcap was taking locks in the wrong order resulting in deadlocks on close. If you had an xcompcap properties window open on close it was nearly 100% deadlock. This ensures locks are taken in the same order as libobs takes when shutting down. Appears to also fix obsproject#2645
Getting a bit late for me, but applying #3782 appears to fix this (at least doesnt occur out of 40 tries compared to 1:3 chance of triggering before). |
Still having this Issue:
installed from: deb http://ppa.launchpad.net/obsproject/obs-studio-unstable/ubuntu focal main obs_crash_Webcam_Settings_gdb_output.txt Reproduction:
Happens at 100% chance on my system |
Try #4576 if you can compile which is trying to fix another issue that might cause this kind of failure. |
Yes, #4576 fixes it, but will it be merged? Or should this issue be reopened? Release 27.0.1 is still crashing. |
When it's changed from draft to ready for review it'll likely be merged |
Hello. To relaunch this ticket: I have a randomly crash when I close a window (filter window, properties, projector window etc ...).
Do you think #4576 can be used in production ? Thanks ! OBS 27.0.1 |
Hi all, updating this thread to say that #4576 is looking to be released soon. Thanks for testing! |
Platform
Operating system and version:
OBS Studio version:
OBS 25.0.3 (linux)
Package
Followed official installation instructions for Ubuntu.
I did not install
ffmpeg
but I believe I already had it (and I was able to record a couple of videos without problem).Expected Behavior
Not to randomly crash.
Current Behavior
Application crashes.
Steps to Reproduce
Happens randomly, this sometimes works fine. I've also been able to change settings without it crashing.
I'm using two video sources:
Other Info
I'm using two 4k displays, scaled to 200%. Under
Video
in the settings I've configured both the Base (Canvas) Resolution and Output (Scaled) Resolution to3840x2160
. I had to manually enter the number, as the maximum resolution that the dropdown displayed was 1920x1080. Recording with 1920x1080 resolution cut the screen in half (in both axes, thus 1/4 of the screen).Update: happens too if not using display scaling.
The text was updated successfully, but these errors were encountered: