Bug 736135 – rygel becomes unresponsive

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 736135 - rygel becomes unresponsive


Summary:	rygel becomes unresponsive


Status:	RESOLVED DUPLICATE of bug 734358

Product:	rygel
Classification:	Applications
Component:	general
Version:	0.22.x
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	rygel-maint
QA Contact:	rygel-maint

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2014-09-05 15:04 UTC by Debarshi Ray
Modified:	2014-09-08 16:52 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Debarshi Ray 2014-09-05 15:04:01 UTC

I am sorry for the vague summary, but let me try to describe it.

I am hitting this when trying to test the code for:
https://wiki.gnome.org/ThreePointThirteen/Features/BrowseDMSPhotos

I have rygel running on a second laptop serving a folder full of images. It shows up as /com/intel/dLeynaServer/server/1 on my first laptop that is running dleyna-server. I call SearchObjects on its org.gnome.UPnP.MediaContainer2 interface with these arguments:
  'Type = "image.photo"', 0, 0, ['URLs']

This gives me a bunch of URLs (eg., http://192.168.0.16:43669/MediaExport/i/YzlkMjc0NDFhZjA2MGVjNjBmZDc4OTI0NTFiYzc4ZmU%3D.JPG) , but when I try to open one of them in a browser either it loads part of the image or nothing at all.

At this point if I call Rescan and then GetServers on the /com/intel/dLeynaServer object, then it does not show any servers.

I have:
dleyna-server-0.4.0
gupnp-0.20.12
rygel-0.22.3
libsoup-2.46.0

Comment 1 Debarshi Ray 2014-09-05 15:07:02 UTC

When this happens, rygel is consistently stuck at this backtrace:

(gdb) thread apply all bt

+ Trace 234056

Thread 1 (Thread 0x7ffff7fec880 (LWP 4078))

#0 syscall
at ../sysdeps/unix/sysv/linux/x86_64/syscall.S line 38
#1 g_mutex_lock_slowpath
at gthread-posix.c line 1308
#2 g_mutex_lock
at gthread-posix.c line 1332
#3 rygel_gst_sink_thaw
at rygel-gst-sink.c line 196
#4 _g_closure_invoke_va
at gclosure.c line 831
#5 g_signal_emit_valist
at gsignal.c line 3218
#6 g_signal_emit
at gsignal.c line 3365
#7 soup_message_wrote_chunk
at soup-message.c line 1082
#8 io_run_until
at soup-message-io.c line 458
#9 io_run_until
at soup-message-io.c line 867
#10 io_run
at soup-message-io.c line 937
#11 io_run_ready
at soup-message-io.c line 916
#12 g_main_context_dispatch
at gmain.c line 3064
#13 g_main_context_dispatch
at gmain.c line 3663
#14 g_main_context_iterate
at gmain.c line 3734
#15 g_main_loop_run
at gmain.c line 3928
#16 main
at rygel-main.c line 384
#17 main
at rygel-main.c line 1330
#18 main
at rygel-main.c line 1365

Comment 2 Bastien Nocera 2014-09-08 16:52:51 UTC

Hit the same bug when serving video in bug 734358.

*** This bug has been marked as a duplicate of bug 734358 ***