Bug 5157

Summary:	SIGABRT when starting streaming
Product:	Fedora	Reporter:	Hoggins! <hoggins>
Component:	obs-studio	Assignee:	Momcilo Medic <fedorauser>
Status:	RESOLVED FIXED
Severity:	major	CC:	greggulus, mgansser
Priority:	P1	Flags:	fedorauser: needinfo+
Version:	f29
Hardware:	x86_64
OS:	GNU/Linux
namespace:

Description Hoggins! 2019-02-01 23:24:20 CET

Using obs-studio-22.0.3-3.fc29.x86_64, it is not possible to stream anymore from obs-studio.

NOTE: reverting to obs-studio-22.0.3-2.fc29.x86_64 fixes the issue.

It is *always* reproducible on my machine.

Here is the gdb backtrace from when this happens:

malloc(): invalid size (unsorted)

Thread 1 "obs" received signal SIGABRT, Aborted.
0x00007ffff533453f in raise () from /lib64/libc.so.6
(gdb) bt
#0  0x00007ffff533453f in raise () at /lib64/libc.so.6
#1  0x00007ffff531e895 in abort () at /lib64/libc.so.6
#2  0x00007ffff5377927 in __libc_message () at /lib64/libc.so.6
#3  0x00007ffff537e25c in  () at /lib64/libc.so.6
#4  0x00007ffff53811d4 in _int_malloc () at /lib64/libc.so.6
#5  0x00007ffff53838e6 in calloc () at /lib64/libc.so.6
#6  0x00007fffb0de8b00 in  () at /usr//lib64/obs-plugins/obs-outputs.so
#7  0x00007fffb0de8e87 in  () at /usr//lib64/obs-plugins/obs-outputs.so
#8  0x00007fffb0ddf6d1 in  () at /usr//lib64/obs-plugins/obs-outputs.so
#9  0x00007ffff6266a39 in obs_output_create () at /lib64/libobs.so.0
#10 0x00005555556a6d2f in AdvancedOutput::StartStreaming(obs_service*) ()
#11 0x0000555555635f0a in OBSBasic::StartStreaming() ()
#12 0x00005555556363e8 in OBSBasic::on_streamButton_clicked() ()
#13 0x000055555570d389 in  ()
#14 0x000055555570feb3 in OBSBasic::qt_metacall(QMetaObject::Call, int, void**) ()
#15 0x00007ffff5a97147 in QMetaObject::activate(QObject*, int, int, void**) () at /lib64/libQt5Core.so.5
#16 0x00007ffff7b775b6 in QAbstractButton::clicked(bool) () at /lib64/libQt5Widgets.so.5
#17 0x00007ffff7b777de in  () at /lib64/libQt5Widgets.so.5
#18 0x00007ffff7b78c33 in  () at /lib64/libQt5Widgets.so.5
#19 0x00007ffff7b78e05 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () at /lib64/libQt5Widgets.so.5
#20 0x00007ffff7ace378 in QWidget::event(QEvent*) () at /lib64/libQt5Widgets.so.5
#21 0x00007ffff7a8f285 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5
#22 0x00007ffff7a96be8 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5
#23 0x00007ffff5a6eec6 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5
#24 0x00007ffff7a95edd in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () at /lib64/libQt5Widgets.so.5
#25 0x00007ffff7ae9118 in  () at /lib64/libQt5Widgets.so.5
#26 0x00007ffff7aebcbe in  () at /lib64/libQt5Widgets.so.5
#27 0x00007ffff7a8f285 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5
#28 0x00007ffff7a969a0 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5
#29 0x00007ffff5a6eec6 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5
#30 0x00007ffff5e0f4d3 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /lib64/libQt5Gui.so.5
#31 0x00007ffff5e115d5 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /lib64/libQt5Gui.so.5
#32 0x00007ffff5dec70b in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Gui.so.5
#33 0x00007fffe293c85f in  () at /lib64/libQt5XcbQpa.so.5
#34 0x00007ffff5a6de0b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#35 0x00007ffff5a75ed6 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#36 0x00005555555f9598 in main ()

Comment 1 leigh scott 2019-02-09 16:48:50 CET

*** Bug 5165 has been marked as a duplicate of this bug. ***

Comment 2 Momcilo Medic 2019-02-27 19:04:42 CET

Hi Hoggins,

OBS studio 23 was released couple of days ago.

Can you please go ahead and test if the issue persists?

You can grab the RPM files from koji[1] or wait until it hits the repo.

[1] http://koji.rpmfusion.org/koji/buildinfo?buildID=10181

Awaiting your feedback,
Momo.

Comment 3 Momcilo Medic 2019-03-26 17:55:21 CET

Since there are no negative feedback here, I'm assuming it's all OK.