systemd-resolved crashed with SIGSEGV in sd_event_dispatch()

[Jesse]

Unsure what the cause is, but this error occurred after I clicked on a hyperlink on YouTube.com to access one of my subscribed channels.

Running Ubuntu GNOME 16.10 x64 beta 1, GNOME 3.20 desktop environment, kernel 4.4.0-9136-generic.

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: systemd 231-5
ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
Uname: Linux 4.4.0-9136-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Sun Sep 11 17:43:41 2016
ExecutablePath: /lib/systemd/systemd-resolved
InstallationDate: Installed on 2016-08-30 (13 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160824)
MachineType: LENOVO 80SA
ProcCmdline: /lib/systemd/systemd-resolved
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic root=UUID=0ac2b91e-398e-44c3-93be-fdde19739c68 ro quiet splash vt.handoff=7
Signal: 11
SourcePackage: systemd
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /lib/systemd/libsystemd-shared-231.so
 sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so
 sd_event_run () from /lib/systemd/libsystemd-shared-231.so
Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 05/17/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: 0VCN18WW(V1.03)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Lenovo ideapad F
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad FLEX 4-1470
dmi.modalias: dmi:bvnLENOVO:bvr0VCN18WW(V1.03):bd05/17/2016:svnLENOVO:pn80SA:pvrLenovoideapadFLEX4-1470:rvnLENOVO:rnLenovoideapadF:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapadFLEX4-1470:
dmi.product.name: 80SA
dmi.product.version: Lenovo ideapad FLEX 4-1470
dmi.sys.vendor: LENOVO

[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 #1621396, 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.