rhythmbox periodically hangs during playback via SFTP

[Dmitrii Shcherbakov]

Scenario: a server is available via LAN from which content is played back via SFTP (ssh, gvfs).

After some time (could be an hour) rhythmbox hangs and a window comes up suggesting that you can either wait or terminate rhythmbox.

There are no network interruptions that would cause something like this (the issue comes up quite frequently) and plus I do not see any of the threads to be in the D state.

strace shows that there is a futex wait for some condition.

ps:

redacted 20291 3.3 1.0 1989228 173472 tty2 Sl+ 12:14 4:49 rhythmbox

➜ ~ ps -T -o pid,tid,class,rtprio,ni,pri,psr,pcpu,stat,wchan:14,comm -p 20291
  PID TID CLS RTPRIO NI PRI PSR %CPU STAT WCHAN COMMAND
20291 20291 TS - 0 19 6 0.9 Sl+ futex_wait_que rhythmbox
20291 20294 TS - 0 19 6 0.0 Sl+ poll_schedule_ gmain
20291 20295 TS - 0 19 7 0.0 Sl+ poll_schedule_ gdbus
20291 20296 TS - 0 19 7 0.0 Sl+ poll_schedule_ dconf worker
20291 20298 TS - 0 19 2 0.2 Sl+ futex_wait_que typefind:sink
20291 20306 TS - 0 19 5 0.0 Sl+ futex_wait_que rhythmdb-thread
20291 20344 TS - 0 19 4 0.1 Sl+ futex_wait_que id3demux167:sin
20291 20346 TS - 0 19 7 0.1 Sl+ poll_schedule_ mpegaudioparse1
20291 20392 TS - 0 19 4 0.2 Sl+ futex_wait_que mpegaudioparse1
20291 20393 TS - 0 19 4 0.0 Sl+ futex_wait_que id3demux168:sin
20291 12125 TS - 0 19 4 0.0 Sl+ futex_wait_que typefind:sink

sudo strace -f -p 20291
strace: Process 20291 attached with 11 threads
[pid 12125] futex(0x55eacb8dc778, FUTEX_WAIT_PRIVATE, 1, NULL <unfinished ...>
[pid 20393] futex(0x7fe7201320b8, FUTEX_WAIT_PRIVATE, 1, NULL <unfinished ...>
[pid 20392] futex(0x7fe6f4013538, FUTEX_WAIT_PRIVATE, 1, NULL <unfinished ...>
[pid 20346] restart_syscall(<... resuming interrupted poll ...> <unfinished ...>
[pid 20344] futex(0x7fe6f0004898, FUTEX_WAIT_PRIVATE, 1, NULL <unfinished ...>
[pid 20306] futex(0x55eacab00580, FUTEX_WAIT_PRIVATE, 2, NULL <unfinished ...>
[pid 20298] futex(0x55eacb8dcf58, FUTEX_WAIT_PRIVATE, 1, NULL <unfinished ...>
[pid 20296] restart_syscall(<... resuming interrupted poll ...> <unfinished ...>
[pid 20295] restart_syscall(<... resuming interrupted poll ...> <unfinished ...>
[pid 20294] restart_syscall(<... resuming interrupted poll ...> <unfinished ...>
[pid 20291] futex(0x55eacf0ea9a0, FUTEX_WAIT_PRIVATE, 2, NULL <unfinished ...>

# after killing via the GUI button
[pid 20344] <... futex resumed> ) = ? ERESTARTSYS (To be restarted if SA_RESTART is set)
[pid 12125] <... futex resumed>) = ?
[pid 20393] <... futex resumed>) = ?
[pid 20392] <... futex resumed>) = ?
[pid 12125] +++ killed by SIGKILL +++
[pid 20393] +++ killed by SIGKILL +++
[pid 20392] +++ killed by SIGKILL +++
[pid 20346] <... restart_syscall resumed>) = ?
[pid 20344] +++ killed by SIGKILL +++
[pid 20346] +++ killed by SIGKILL +++
[pid 20306] <... futex resumed>) = ?
[pid 20296] <... restart_syscall resumed>) = ?
[pid 20295] <... restart_syscall resumed>) = ?
[pid 20306] +++ killed by SIGKILL +++
[pid 20296] +++ killed by SIGKILL +++
[pid 20298] <... futex resumed>) = ?
[pid 20295] +++ killed by SIGKILL +++
[pid 20298] +++ killed by SIGKILL +++
[pid 20294] <... restart_syscall resumed>) = ?
[pid 20291] <... futex resumed>) = ?
[pid 20294] +++ killed by SIGKILL +++
+++ killed by SIGKILL +++

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: rhythmbox 3.4.2-4ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 4 14:44:50 2018
InstallationDate: Installed on 2018-07-12 (53 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: rhythmbox
UpgradeStatus: No upgrade log present (probably fresh install)

[Sebastien Bacher (seb128)]

Thank you for your bug report. How is the sftp mounting done? Do you use the gvfs location or a fuse mount or similar? Can you access/Read from that mount using e.g nautilus when rhythmbox is blocking?
In any case that's probably an upstream issue and should be reported on https://gitlab.gnome.org/GNOME/rhythmbox/issues/new