obsproject / obsproject/obs-studio

OBS 32 Crashes After Stopping Recording with VAAPI or QuickSync H.264 Encoders

Open
#12,970 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

platform/linux
Dominant language
C
Stars
76.4k
Forks
10.2k
Avg merge
4d 23h
Merged PRs (30d)
12

Description

Operating System Info

Other

Other OS

CachyOS x86_64 + Kernel 6.18.2-2-cachyos

OBS Studio Version

32.0.2

OBS Studio Version (Other)

No response

OBS Studio Log URL

VAAPI: https://obsproject.com/logs/1PcVpQH7NCO6veEU, QS: https://obsproject.com/logs/coYlWTfOrHEKNQce

OBS Studio Crash Log URL

No crash log generated, even though it crashed...

Expected Behavior

When I stop my recording, obs produces the video without crashing.

Current Behavior

When I stop my recording, obs produces the video, but crashes in the process. The video is playable.

Steps to Reproduce
  1. Go To Settings>Output and set Output to Advanced
  2. Go to Recording and set Video Encoder to FFmpeg VAAPI H.264 or Quicksync H.264
  3. Set VAAPI Device to HD Graphics 5500 (If using VAAPI)
  4. Re-launch obs (this is done because the "output fails to save" error is shown after applying settings and starting recording)
  5. Start Recording
  6. End Recording, OBS freezes and crashes (The video exported should still be exported and playable)
    ...
Anything else we should know?

Happens on these encoders:
FFmpeg VAAPI H.264
Quicksync H.264

Might be related, but when apply settings to one of these encoders, I am unable to start the recording and it gives this log: VAAPI, QS

Fastfetch Output (removed name and local ip):

           .-------------------------:                    [Username]@cachyos-elitebook-850-g2
          .+=========================.                    ------------------------------
         :++===++==================-       :++-           OS: CachyOS x86_64
        :*++====+++++=============-        .==:           Host: HP EliteBook 850 G2 (A3008D510B03)
       -*+++=====+***++==========:                        Kernel: Linux 6.18.2-2-cachyos
      =*++++========------------:                         Uptime: 2 hours, 10 mins
     =*+++++=====-                     ...                Packages: 1431 (pacman)
   .+*+++++=-===:                    .=+++=:              Shell: fish 4.3.1
  :++++=====-==:                     -*****+              Display (AUO35ED): 1920x1080 in 16", 60 Hz [Built-in]
 :++========-=.                      .=+**+.              DE: KDE Plasma 6.5.4
.+==========-.                          .                 WM: KWin (Wayland)
 :+++++++====-                                .--==-.     WM Theme: Breeze
  :++==========.                             :+++++++:    Theme: Breeze (Dark) [Qt], Breeze-Dark [GTK2], Breeze [GTK3]
   .-===========.                            =*****+*+    Icons: breeze-dark [Qt], breeze-dark [GTK2/3/4]
    .-===========:                           .+*****+:    Font: Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK2/3/4]
      -=======++++:::::::::::::::::::::::::-:  .---:      Cursor: breeze (24px)
       :======++++====+++******************=.             Terminal: konsole 25.12.0
        :=====+++==========++++++++++++++*-               CPU: Intel(R) Core(TM) i5-5200U (4) @ 2.70 GHz
         .====++==============++++++++++*-                GPU 1: AMD Radeon R7 M260X [Discrete]
          .===+==================+++++++:                 GPU 2: Intel HD Graphics 5500 @ 0.90 GHz [Integrated]
           .-=======================+++:                  Memory: 3.05 GiB / 7.63 GiB (40%)
             ..........................                   Swap: 13.00 MiB / 7.63 GiB (0%)
                                                          Disk (/): 15.34 GiB / 29.73 GiB (52%) - btrfs
                                                          Local IP (wlan0): [LocalIP]
                                                          Battery (Primary): 100% [AC Connected]
                                                          Locale: en_GB.UTF-8

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the two linked OBS logs and reproduce the failure through Settings > Output > Recording using FFmpeg VAAPI H.264 and QuickSync H.264. Compare the stop-recording behavior and the related settings-apply failure; done means OBS no longer freezes or crashes and the resulting video remains playable.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
audio-video-rtc, desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.