atop crashed with SIGSEGV in __libc_start_main()

[Ian! D. Allen]

I'd never seen this before. ATOP was dying before even getting started, according to GDB. Six hours later, it works fine.
At the time, I had some very memory- and disk-intensive processes running, moving 20GB files around.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: atop 1.26-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Sat Sep 24 03:56:43 2011
ExecutablePath: /usr/bin/atop
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: atop
SegvAnalysis:
 Segfault happened at: 0x7f6dcf31b80f: rep stos %rax,%es:(%rdi)
 PC (0x7f6dcf31b80f) ok
 source "%rax" ok
 destination "%es:(%rdi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: atop
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
 __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
 ?? ()
Title: atop crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout disk lpadmin plugdev sambashare video

[Apport retracing service (apport)]

StacktraceTop:
 __memset_x86_64 () at ../sysdeps/x86_64/multiarch/../memset.S:1286
 engine () at /usr/include/bits/string3.h:85
 main (argc=<optimized out>, argv=<optimized out>) at atop.c:651

[Launchpad Janitor (janitor)]

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

[martin suchanek (martin-suc)]

Affects ubuntu vivid

[D (360-dennis)]

I'm on 15.04 and i experienced this as well

[martin suchanek (martin-suc)]

Affects ubuntu wily 15.10

[Viktor Pal (deere)]

Having this on 15.04, atop is running as a daemon to collect information, but crashes from time to time.

As atop has no systemd script but is started using sysinit unfortunately.
That is a pity as systemd could nicely respawn it when this happens with minimizing the impact...

[Lonnie Lee Best (launchpad-startport)]

One thing I'd like to mention. I login as soon as Ubuntu will allow it. The login screen pops up and then goes away briefly. During that going-away time, I go ahead an enter my login credentials, and I'm usually logged in by the time the start up sound drums. As a matter of fact, the drum-sound is slightly cropped off at the end because I'm logged in before is completely sound (I think).