atop crashed with SIGFPE in acctprocnt()

[Nazar Mokrynskyi]

Didn't use it, but looks like something in background crashed.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: atop 1.26-2
Uname: Linux 3.17.0-rc6-haswell x86_64
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Thu Sep 25 00:00:01 2014
ExecutablePath: /usr/bin/atop
InstallationDate: Installed on 2012-04-27 (880 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423)
ProcCmdline: /usr/bin/atop -a -w /var/log/atop/atop_20140925 600
Signal: 8
SourcePackage: atop
StacktraceTop:
 ?? ()
 ?? ()
 __libc_start_main (main=0x402c70, argc=5, argv=0x7fff99f75128, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff99f75118) at libc-start.c:287
 ?? ()
Title: atop crashed with SIGFPE in __libc_start_main()
UpgradeStatus: Upgraded to utopic on 2013-05-12 (500 days ago)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 acctprocnt () at acctproc.c:598
 engine () at atop.c:815
 main (argc=<optimized out>, argv=<optimized out>) at atop.c:651

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Mark Preston (emarkpreston)]

First occurrence of this "atop crashed with SIGFPE" on my Xenial Xerus is 23Jun16. OS ran without this flaw until that date.

[Nestor Abraham (nesk8)]

Started to occur only after System suspend or a system start after a shutdown for me. It doesn't reproduce when restarting.