Hang on Close, must be killed, offers Safe Mode next startup. No crash dump.

A

AaronD

Active Member
Is there something besides the logfile (which isn't all that useful to me but might be to someone else), and just trial-and-error deleting stuff and adding back until the culprit is found?

Analyzer | OBS

OBS (Open Broadcaster Software) is free and open source software for video recording and live streaming. Stream to Twitch, YouTube and many other providers or record your own videos with high quality H264 / AAC encoding.
obsproject.com obsproject.com

Since that log was made, I updated the Advanced Scene Switcher plugin, because its notes said it "Fixed a crash on shutdown." It did its new-version offer to backup the settings, but the hang on close is still there.

I have a similar Profile and Scene Collection that don't hang on close, which tells me that the mere presence of all of my plugins isn't a problem. But their settings could still be suspect, along with OBS's native settings. Is there a compare tool beyond a standard text-based diff viewer in ~/.config/obs-studio/basic/{profiles|scenes}, to tell me what to add to add/delete/change between the good one and the bad one? (after duplicating of course!)
 
This sounds like a job for GDB and then check where it gets stuck. Pasting the OBS Bot factioid in case you want to follow up.

If you're on a native package (like the Ubuntu PPA), skip to step 3.
  1. Install requirements: flatpak install org.kde.Sdk/x86_64/6.8 com.obsproject.Studio.Debug
  2. Run flatpak run --command=sh --devel com.obsproject.Studio
  3. Run gdb obs
  4. Once you are in the (gdb) prompt run set logging enabled on
  5. In the (gdb) prompt run run
  6. This will download a bunch of additional debug information on first run, just wait for it to finish
  7. Once OBS starts, reproduce your crash
  8. Once crashed OBS will freeze. In the (gdb) prompt run bt full
  9. To get out of gdb run exit
    • If you are on Flatpak: run exit again to get out of the Flatpak
  10. Upload the gdb.txt to Discord
Click to expand...

In your case you want to make it hang, then go to the GDB window and hit ctrl-c, then "bt full"
 
Tuna said:
This sounds like a job for GDB and then check where it gets stuck. Pasting the OBS Bot factioid in case you want to follow up.



In your case you want to make it hang, then go to the GDB window and hit ctrl-c, then "bt full"
Click to expand...
Here's a backtrace, from line 1174 to the end.

X in the corner, see it hang, switch to terminal and Ctrl+C (lines 1174 to 1177), then bt full (lines 1178 to end) and exit.
 

Attachments

Tuna said:
Perhaps similar issue as https://github.com/obsproject/obs-studio/issues/13495
Click to expand...
Maybe, but I have my doubts:
  • That issue says it can't be reproduced. Mine happens every time with this Profile and Scene Collection.
  • I'm not renaming anything. A possible connection *might* exist in the form of not closing correctly, but only if renaming involves a close and re-open.
    • According to that theory, the log entry that the linked issue is missing, would likely come in the middle, as in:
      1. Close (hang here)
      2. Rename files
      3. Log success
      4. Re-open new name
    • If that were true, then hanging on close would indeed not produce the log entry, like the linked issue says.
 
Last edited:
AaronD said:
Here's a backtrace, from line 1174 to the end.

X in the corner, see it hang, switch to terminal and Ctrl+C (lines 1174 to 1177), then bt full (lines 1178 to end) and exit.
Click to expand...
Hi, I'm the one whose bug you linked to. I can't say what's causing your bug.

You're missing all stack frames belonging to the obs binary, including the one calling into obs_wait_for_destroy_queue. Could you install debug symbols for obs (obs-studio-dbgsym?) and take another backtrace?
 
nyanpasu64 said:
You're missing all stack frames belonging to the obs binary, including the one calling into obs_wait_for_destroy_queue. Could you install debug symbols for obs (obs-studio-dbgsym?) and take another backtrace?
Click to expand...
In progress...

Bash: 
$ sudo apt install obs-studio-dbgsym
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package obs-studio-dbgsym
$
A bit of googling says that *is* the correct name. But then I remembered that I'm on a slightly older version than current (32.1.0, compared to 32.1.2), so I went back to the official download page:
github.com

Releases · obsproject/obs-studio

OBS Studio - Free and open source software for live streaming and screen recording - obsproject/obs-studio
github.com github.com
Currently downloading about 1GB from there: debug symbols for my current version, and both the release and debug versions of the official current. That's going to take a while...

(I'm intentionally older than current, because the devs have a history of breaking things without warning or care. But if there's already a problem with what I have, that can be a reason to try something newer. *Maybe* it just happens to be fixed, but something tells me it isn't. We'll see. If not, I'll have a bug report for the latest code.)
 
You must log in or register to reply here.
Back
Top