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
OBS crash: Buffer overflow detected #219
Comments
I just noticed, that my hardware doesn't fullfill the minimum requirements for StreamFX. Closing the issue... |
Your hardware is within the specs, at least if nothing else is also using that GPU. Did you have any filters or similar enabled at the time of testing? |
I attempted to start OBS once again after deleting all sources (so I basically had an entirely empty scene). Is there an easy way to rule out a graphics driver issue? As you might now, Nvidia Optimus on Linux is a pain in the ass :P |
Use the Upload Last Log feature in OBS Help menu, and post the URL here, that might help determine possible problems. |
@skeletonbow I had a look at the log files. Unfortunately, there's even less information than in the startup output (stdout):
|
Does OBS not create crash logs on linux? On Windows it creates extensive crash logs that include a stack trace. |
Sooo... I built StreamFX from source again (this time with obs-studio; previously I tried to build it as standalone) and that works. Let me know if you plan to troubleshoot this further and if I can be of any assistance. If not, as far as I'm concerned, this ticket can be closed. Thanks for your help, anyways :) |
@theCalcaholic Which GCC version did you originally use? gcc8 is for 18.04, gcc9 is for 19.10 and beyond. |
I was using gcc8 |
Does this still happen with the recent binaries? |
Given the lack of a reply for more than 14 days, I assume this is no longer the case. Closing. |
Description
After installing the StreamFX plugin, obs crashes with the following log output:
System Information
Note: I also tested the 'clang' version from the releases page, which failed with the error described in #155
The text was updated successfully, but these errors were encountered: