Closed mymedia2 closed 6 years ago
PulseAudio buffer sizes likely. Do you have any other active audio streams when this happens? Did it crash like this in the previous versions or it only started in 2.1.1?
Really! I was just listening music. But a strange speech-dispatcher process was running, and after killall speech-dispatcher
the problem disappears or is hardly non-reproducible. To be clear, I use Ubuntu 16.04 (this is a host system), and I run Telegram inside chroot jail with Debian Unstable.
In older versions of libtgvoip I got the next error.
Assertion '!m->thread || !pa_thread_is_running(m->thread) || !in_worker(m)' failed at pulse/thread-mainloop.c:187, function pa_threaded_mainloop_unlock(). Aborting.
Theoretically, the issue may have been linked with that speech-dispatcher...
In older versions of libtgvoip I got the next error.
So at least it gets further now lol
I wonder if PulseAudio would be okay with me disregarding the requestedBytes value and always writing at most 60ms of audio at a time.
Should be fixed in 2.2.2 btw. I'll close this issue as soon as tdesktop beta with 2.2.2 comes out.
Actually, it did come out a while ago now
Hi,
The following crash occurs at the beginning of a call. What can cause this error?
Stacktrace:
libtgvoip version: 2.1.1 Telegram Desktop version: 1.3.10