OBS becomes unresponsive when adding a second scene to a custom vertical canvas
I'm experiencing a reproducible issue with SE.Live custom vertical canvases. OBS becomes completely unresponsive when a second scene is added to a custom canvas, even when both scenes are completely empty.
This also affects my original vertical canvas, which contains five scenes.
System information
- OBS Studio: 33.0.1 (64-bit, Windows)
- SE.Live versions tested: 26.10.6.1039 and 26.10.1.1037
- Operating system: Windows 11, build 26300 (26H2)
- CPU: AMD Ryzen 9 9950X3D
- GPU: NVIDIA GeForce RTX 4060
- RAM: 32 GB
- Canvas resolution: 1080 × 1920
- Video encoder: NVIDIA NVENC H.264
Steps to reproduce
- Open OBS normally with SE.Live enabled.
- Create a new custom vertical canvas (1080 × 1920).
- Keep the default single empty scene.
- Save and restart OBS. It works correctly.
- Rename the first scene (for example, to
STARTING 1). It still works. - Create a second empty scene (for example,
ACABANDO). - Save and restart OBS.
After adding the second scene, OBS becomes unresponsive and displays "Not Responding".
Additional tests
I also tested my original five-scene vertical canvas:
- Removing all browser sources did not fix the issue.
- Removing all sources, including media, camera and window capture sources, did not fix the issue.
- Creating a new canvas with only one empty scene works correctly.
- Creating a second empty scene in that new canvas reproduces the issue.
- Changing the canvas ID and regenerating scene/source IDs in the JSON did not resolve the original problem.
- OBS works correctly in Safe Mode.
The issue has been reproduced with two different SE.Live versions, 26.10.6.1039 and 26.10.1.1037.
Relevant log information
OBS reports that startup has completed successfully:
==== Startup complete ===============================================
The SE.Live plugin then initializes. The log also contains these messages:
Attempted to rename context to duplicate name
QDockWidgetLayout::addItem(): please use QDockWidgetLayout::setWidget()
However, there is no explicit crash stack trace in the provided log. OBS simply becomes unresponsive.
Expected behaviour
Custom vertical canvases should support multiple independent scenes, just like normal OBS scene collections.
Adding a second empty scene should not cause OBS to freeze or become unresponsive.
Actual behaviour
A custom vertical canvas with one empty scene works. As soon as a second empty scene is created, OBS becomes unresponsive.
Could you investigate whether this is a bug in the custom canvas scene-management system, particularly when registering or loading multiple scenes?
I can provide the JSON files for both the working one-scene canvas and the failing two-scene canvas, as well as the full OBS logs.
Please sign in to leave a comment.
Comments
0 comments