bogofilter-bdb assert failure: *** Error in `/usr/bin/bogofilter': realloc(): invalid next size: 0x00000000019564c0 ***

[Removed by request]

Unknown, auto reported

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: bogofilter-bdb 1.2.4+dfsg1-4build1
ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
Uname: Linux 4.4.0-14-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AssertionMessage: *** Error in `/usr/bin/bogofilter': realloc(): invalid next size: 0x00000000019564c0 ***
CurrentDesktop: GNOME
Date: Sun Mar 20 10:33:12 2016
ExecutablePath: /usr/bin/bogofilter-bdb
InstallationDate: Installed on 2016-03-20 (0 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225.1)
ProcCmdline: /usr/bin/bogofilter --unicode=yes
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: bogofilter
StacktraceTop:
 __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7f58105dc2e8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
 malloc_printerr (ptr=0x7ffd3aac2230, str=0x7f58105d853e "realloc(): invalid next size", action=1) at malloc.c:4965
 _int_realloc (av=av@entry=0x7f581080fc00 <main_arena>, oldp=oldp@entry=0x19564b0, oldsize=oldsize@entry=16480, nb=nb@entry=16544) at malloc.c:4219
 __GI___libc_realloc (oldmem=0x19564c0, bytes=16525) at malloc.c:3023
 ?? ()
Title: bogofilter-bdb assert failure: *** Error in `/usr/bin/bogofilter': realloc(): invalid next size: 0x00000000019564c0 ***
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip 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 #1554582, 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.