named crashed with SIGABRT in isc_assertion_failed()

[LAZA]

Steps to reproduce:
- start VM
- login
- wait same seconds/a minute

Don't know what happended...

.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: bind9 1:9.10.3.dfsg.P2-5
ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
Uname: Linux 4.4.0-13-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Tue Mar 15 19:09:38 2016
ExecutablePath: /usr/sbin/named
InstallationDate: Installed on 2015-10-28 (139 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151028)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic root=UUID=ecbb2a31-eac1-4c14-870a-90cb95d15d67 ro quiet splash
ProcEnviron:
 LANG=de_DE.UTF-8
 PATH=(custom, no user)
RelatedPackageVersions:
 bind9utils 1:9.10.3.dfsg.P2-5
 apparmor 2.10-3ubuntu2
Signal: 6
SourcePackage: bind9
StacktraceTop:
 ?? ()
 isc_assertion_failed () from /usr/lib/x86_64-linux-gnu/libisc.so.160
 isc.mem_destroy () from /usr/lib/x86_64-linux-gnu/libisc.so.160
 isc_mem_destroy () from /usr/lib/x86_64-linux-gnu/libisc.so.160
 ?? ()
Title: named crashed with SIGABRT in isc_assertion_failed()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

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