Bug 222116 - sysutils/atop core dumps after a few minutes
Summary: sysutils/atop core dumps after a few minutes
Status: Closed Unable to Reproduce
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-07 07:31 UTC by Sam
Modified: 2018-01-17 07:58 UTC (History)
1 user (show)

See Also:
samm: maintainer-feedback+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sam 2017-09-07 07:31:28 UTC 
On FreeBSD 11.1-RELEASE, atop core dumps after a few minutes. Sometimes it may take a bit longer.

It is installed from "latest" pkg repository (Version: 2.0.2), on HP z620 with Xeon CPU E5-1650 and 16GB ECC ram.

When launched as a service, after a few minutes I get:

$ sudo service atop start
Starting atop.

$ Malloc failed for compression buffer
Comment 1 Sam 2017-09-10 12:52:47 UTC 
Further details:

Yesterday I tried leaving a terminal open with atop running from cli (atop as service being not running, since it dumped core).

This morning atop was still running with no issues.

So, it seems the issue happens only when atop is launched as service.

I am experiencing this not only on local workstations, but also headless servers.
Comment 2 Oleksii Samorukov freebsd_committer freebsd_triage 2017-12-28 09:40:26 UTC 
Please share core dump, i will take a look
Comment 3 Sam 2017-12-28 12:09:39 UTC 
(In reply to samm from comment #2)

Hi,

I have uploaded atop.core (11.4 Mb) here:

https://box.forumcivico.com/cloud/index.php/s/NmP4WRe4XgL2eCy

Thanks for taking a look.
Comment 4 Sam 2018-01-16 15:47:18 UTC 
I have been monitoring atop, and I must say it does not dumo core anymore.

So, it could be the issue was on some other part of the servers environment.

I will continue monitoring atop and report back in case I see issues. We do have atop running as service on all of our servers (about a dozen at the moment)