dleyna-renderer-service crashed with SIGSEGV in dlr_device_unsubscribe()

[Talpah]

ubuntu gnome 15.04 fresh install, then `do-release-upgrade -d` to 15.10. I was using Gnome Maps when it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: dleyna-renderer 0.4.0-1
ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
Uname: Linux 4.2.0-14-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Oct 8 23:36:15 2015
ExecutablePath: /usr/lib/dleyna-renderer/dleyna-renderer-service
InstallationDate: Installed on 2015-10-08 (0 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/lib/dleyna-renderer/dleyna-renderer-service
SegvAnalysis:
 Segfault happened at: 0x7f86348efe68 <dlr_device_unsubscribe+40>: mov (%rax,%rdx,8),%rdi
 PC (0x7f86348efe68) ok
 source "(%rax,%rdx,8)" (0x4d53fd8948555441) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: dleyna-renderer
StacktraceTop:
 dlr_device_unsubscribe () from /usr/lib/x86_64-linux-gnu/dleyna-renderer/libdleyna-renderer-1.0.so.1
 dlr_upnp_unsubscribe () from /usr/lib/x86_64-linux-gnu/dleyna-renderer/libdleyna-renderer-1.0.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/dleyna-renderer/libdleyna-renderer-1.0.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libdleyna-core-1.0.so.3
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: dleyna-renderer-service crashed with SIGSEGV in dlr_device_unsubscribe()
UpgradeStatus: Upgraded to wily on 2015-10-08 (0 days ago)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1440509, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.