[Source Properties] Crash / Progression Block - Adding, removing, and editing sources and starting streams leads to crash

[realsinse420]

I tried adding a new browser source (https://minipadder.link/) that shows controller input on-screen. This lead to a crash.
After relaunching OBS Studio, I tried removing the source which was still present. This lead to yet another crash. With many attempts, I eventually succeeded in modifying the scenes a bit but I was unable to begin streaming and gave up.

STR:
1- Install the application (26.0.2 64-bit)
2- Add a few types of sources, and finally a browser source set to 256 x 144 and the link: https://minipadder.link/
3- Observe issue
4- Relaunch the application
5- Try to edit, add, or remove sources, or begin a stream or recording
6- Observe issue

Results:
The application and all windows except the VST plugin windows freeze, and after 2-10 seconds the application crashes.
Sometimes some or all new changes to the profile since last launch are lost.

Note:
OBS Studio was previously rather stable, and seems to have degraded in performance over the last 70 or so hours of use since first downloading and installing it.

OBS seems to be getting stuck in a loop when the discord plugin fails to connect and OBS was not able to catch the looping function. Attempting to delete the discord plugin causes a crash creating a progression block.

Question:
Is it possible to remove the discord plugin manually via configuration files without causing any issues?

 

[realsinse420]

when attempting to delete the discord plugin, here is the log for that crash.

 

[realsinse420]

Note, in STR, when adding sources, ensure to add the discord streamkit before adding the minipadder plugin.

 

[R1CH]

Can you also include the crash log?

 

[realsinse420]

In the appdata files, the crash folder was never populated with any files. Whatever error handling that is meant to produce the log fails to do so with these STR. Is there an other easy way I can get you the stack-trace while reproducing the bug, since crash reports are not an option?

I'm familiar with BASH but I don't really know my way around DOS nor Powershell.

 

[realsinse420]

The best I can provide at the moment are dump files created with Process Explorer while OBS is stuck in the loop. The root process was used to create the dump files, but they are too large to upload here and I do not have software to view them and extract the stack trace.

I tried manually removing the discord plugin from the scene .json file, and that succeeded, however the crash is still occurring now. However, there is no longer a period of freezing before the crash. The processes now just instantly are killed. There is still no crash log produced, only this regular log:

 

[realsinse420]

I have completely re-installed the application, backing up and finally replacing only the appdata/roaming/obs-studio/basic folder afterwards.

This did not resolve the issue either. There must be a corrupted local file causing these issues I would imagine or something along those lines?

 

[realsinse420]

I think I found the bug @R1CH . The VST plugin (Youlean Loudness meter) had an "chunk_data" property in the scene's .json file that was being written to constantly. There must be some function involved in resolving the chunk_data that is appending instead of replacing the variable.

There was almost 700,000 Kb of text data written to that single chunk_data property in the json file.

 

[realsinse420]

I have copied the json and renamed it (in-file and file-name), removed the offending vst from the json, and rebooted obs studio into that scene collection. The issue is resolved!

For anyone looking through this for answers.

Go to %appdata% in your explorer, then obs-studdio, then basic, finally "scenes".

Open the .json file of the scene you are using when the app crashes and open it with notepad.

Scroll through looking for long portions of text.

When you find one, remove the entire section from '[' to ']', keeping the correct syntax.

This may resolve your issue.

 

[R1CH]

Yikes, that isn't good. Perhaps we should limit maximum data length in the config files :D

 

[bpmacedo]

Hi!

I know this thread is a bit old but joined only to thank you here!

Got problems to edit, remove, add anything on my scenes or even start streaming and didn't know what to do. I can confirm the plugin is the offense here and I found another solution to clear the information on "chunk_data" section.

Just open "Youlean" interface on OBS and click on the red button with X inside.

After doing that and close OBS the size of my .json file decreased a lot!!!

Thx 4 all!