Version-Release number of selected component: dleyna-renderer-0.5.0-4.fc24 Additional info: reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: /usr/libexec/dleyna-renderer-service crash_function: g_hash_table_lookup_node executable: /usr/libexec/dleyna-renderer-service global_pid: 19171 kernel: 4.6.4-301.fc24.x86_64 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 g_hash_table_lookup_node at ghash.c:373 #5 g_hash_table_insert_internal at ghash.c:1227 #6 prv_device_chain_end at upnp.c:85 #7 prv_free_cb at libdleyna/core/task-processor.c:103 #8 g_hash_table_remove_all_nodes at ghash.c:548 #10 g_hash_table_unref at ghash.c:1097 #11 dleyna_task_processor_free at libdleyna/core/task-processor.c:136 #12 prv_context_free at libdleyna/core/main-loop.c:108 #13 dleyna_main_loop_start at libdleyna/core/main-loop.c:167 #15 _start Potential duplicate: bug 1220876
Created attachment 1184105 [details] File: backtrace
Created attachment 1184106 [details] File: cgroup
Created attachment 1184107 [details] File: core_backtrace
Created attachment 1184108 [details] File: dso_list
Created attachment 1184109 [details] File: environ
Created attachment 1184110 [details] File: limits
Created attachment 1184112 [details] File: maps
Created attachment 1184113 [details] File: mountinfo
Created attachment 1184114 [details] File: namespaces
Created attachment 1184115 [details] File: open_fds
Created attachment 1184117 [details] File: proc_pid_status
Created attachment 1184118 [details] File: var_log_messages
*** Bug 1220876 has been marked as a duplicate of this bug. ***
*** Bug 1319000 has been marked as a duplicate of this bug. ***
In frame #2, we are hitting this assertion: hash_table->ref_count > 0 Thread 1 (Thread 0x7ff4a581c880 (LWP 19171)): #0 0x00007ff4a32f56f5 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 resultvar = 0 pid = 19171 selftid = 19171 #1 0x00007ff4a32f72fa in __GI_abort () at abort.c:89 save_stage = 2 act = {__sigaction_handler = {sa_handler = 0x0, sa_sigaction = 0x0}, sa_mask = {__val = {0, 94, 94689405002016, 95, 140688698862752, 140688696272048, 140735615381008, 94689411297920, 140688686850732, 94689405002016, 140688690240256, 95, 140688698862752, 140688696272048, 94689405002016, 95}}, sa_flags = -1544852320, sa_restorer = 0x7ff4a3c3e4b0 <__func__.10228>} sigs = {__val = {32, 0 <repeats 15 times>}} #2 0x00007ff4a3c17f05 in g_assertion_message (domain=domain@entry=0x7ff4a3c3988e "GLib", file=file@entry=0x7ff4a3c3e212 "ghash.c", line=line@entry=373, func=func@entry=0x7ff4a3c3e4b0 <__func__.10228> "g_hash_table_lookup_node", message=message@entry=0x561e98bec300 "assertion failed: (hash_table->ref_count > 0)") at gtestutils.c:2429 lstr = "373\000\377\177\000\000\000I,\215\317\347mvPAU\230\036V\000\000\370\341\303\243\364\177\000" s = 0x561e98596120 "" #3 0x00007ff4a3c17f9a in g_assertion_message_expr (domain=domain@entry=0x7ff4a3c3988e "GLib", file=file@entry=0x7ff4a3c3e212 "ghash.c", line=line@entry=373, func=func@entry=0x7ff4a3c3e4b0 <__func__.10228> "g_hash_table_lookup_node", expr=expr@entry=0x7ff4a3c3e1f8 "hash_table->ref_count > 0") at gtestutils.c:2452 s = 0x561e98bec300 "assertion failed: (hash_table->ref_count > 0)" #4 0x00007ff4a3be0f36 in g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0x561e98ca21c0, hash_table=0x561e985899e0) at ghash.c:373 hash_table = 0x561e985899e0 key = 0x561e98ca21c0 hash_return = <synthetic pointer> node_hash = <optimized out> hash_value = <optimized out> have_tombstone = 0 step = 0 node_index = <optimized out> first_tombstone = 0 #5 g_hash_table_insert_internal (hash_table=0x561e985899e0, key=0x561e98ca21c0, value=0x561e98a581f0, keep_new_key=0) at ghash.c:1227 key_hash = <optimized out> #6 0x00007ff4a541f4fb in prv_device_chain_end (cancelled=<optimized out>, data=0x561e98e3acb0) at upnp.c:85 device = 0x561e98a581f0 priv_t = 0x561e98e3acb0 #7 0x00007ff4a520c690 in prv_free_cb (data=0x561e98b97280) at libdleyna/core/task-processor.c:103 task_queue = 0x561e98b97280
*** Bug 1258636 has been marked as a duplicate of this bug. ***
*** Bug 1331404 has been marked as a duplicate of this bug. ***
*** Bug 1215332 has been marked as a duplicate of this bug. ***
*** Bug 1359750 has been marked as a duplicate of this bug. ***
*** Bug 1287072 has been marked as a duplicate of this bug. ***
This is caused by dleyna_task_processor_t->on_quit_cb being run while there are still queues present in the processor. Filed as https://github.com/01org/dleyna-core/pull/49
Similar dleyna-server bug: https://bugzilla.redhat.com/show_bug.cgi?id=1205574
dleyna-core-0.5.0-4.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-8b47d28f07
dleyna-core-0.5.0-3.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-d3927e6a71
dleyna-core-0.5.0-4.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-603b9f4445
dleyna-core-0.5.0-4.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
dleyna-core-0.5.0-4.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
dleyna-core-0.5.0-3.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.