Atoptool
atop Crash with: Malloc failed for new pinfo, also Error opening terminal: xterm-256color
Starting atop as non-root, results usually in "Malloc failed for new pinfo", and sometimes instead in "Error opening terminal: xterm-256color.".
Using htop and top instead works fine in same place (also as same user, non-root).
atop -V Version: 2.3.0 - 2017/03/25 09:59:59
testfiber@Blitz:~$ atop ; free ; uname -a ; lsb_release -a ; ps aux | wc -l
Error opening terminal: xterm-256color.
total used free shared buff/cache available
Mem: 65917596 46154740 1283056 3684 18479800 19018152 Swap: 33554428 3030272 30524156
Linux Blitz 4.18.0-2-amd64 #1 SMP Debian 4.18.10-2 (2018-10-07) x86_64 GNU/Linux
No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux testing (buster) Release: testing Codename: buster
726
testfiber@Blitz:~$ atop Malloc failed for new pinfo
testfiber@Blitz:~$ atop ; free ; uname -a ; lsb_release -a ; ps aux | wc -l Malloc failed for new pinfo total used free shared buff/cache available Mem: 65917596 46208788 1222880 3704 18485928 18964156 Swap: 33554428 3030016 30524412
Linux Blitz 4.18.0-2-amd64 #1 SMP Debian 4.18.10-2 (2018-10-07) x86_64 GNU/Linux
No LSB modules are available.
Distributor ID: Debian Description: Debian GNU/Linux testing (buster) Release: testing Codename: buster
726
Can you provide the output of the command "ulimit -Sa"? And can you run "strace -f -o /tmp/atop.trace atop" and provide the last 100 lines of the file /tmp/atop.trace ?
I had the same problem on a fresh ubuntu 18.10 installation. Version 2.3 from apt would not work when its run as a user, only as root. Compiled version 2.4.0 and that one seems to work.
For whats is worth there is the trace: https://gist.github.com/axon-consultancy/3ab44d648f70580271a073e5b699c900
