https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256507
Mark Johnston changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256507
Eugene Grosbein changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256507
Slava changed:
What|Removed |Added
CC||slava.koko...@gmail.com
--- Comment #19 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256507
--- Comment #18 from d...@jetcafe.org ---
Created attachment 236137
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=236137&action=edit
Output of sysctl vm hw
> Can you tell me all the major services that are running on the host?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256507
--- Comment #17 from Tom Jones ---
Can you provide the output of:
sysctl vm hw
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256507
--- Comment #16 from Tom Jones ---
Can you tell me all the major services that are running on the host? This would
help to try and get a simple reproduction environment.
The page count from your first comment suggests this is a machine wi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256507
--- Comment #15 from d...@jetcafe.org ---
I should also mention this wonderful tool prometheus_sysctl_exporter(8). I have
this data ingested into prometheus at a 5 second interval for both machines
here that suffer from this bug. If anyone i
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256507
--- Comment #14 from d...@jetcafe.org ---
So I only wrote the script for the purposes of addressing comment 11. My main
source of data is said sysctls exported at intervals to prometheus, which is
where I get the graph you can look at in the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256507
--- Comment #13 from Helge Oldach ---
This script might yield negative results because of lazy dequeuing of wired
pages which may result into double counting pages occasionally. See bug
#234559.
Perhaps you are just observing similar artif
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256507
--- Comment #12 from d...@jetcafe.org ---
So...stopping -all- running services to me is an effective reboot. :)
Nevertheless, on my machine with the most minimal service deployment that has
the memory issue, I stopped the biggest memory con
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256507
Tom Jones changed:
What|Removed |Added
CC||t...@freebsd.org
--- Comment #11 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256507
--- Comment #10 from Andriy Gapon ---
I have to correct my comment #7, the suspect application is not a Go program,
it's actually a Mono program. Somehow I confused those two things.
Anyway, the problem is still present 13.1-STABLE 689d65
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256507
--- Comment #9 from Bane Ivosev ---
(In reply to dave from comment #8)
Just for the record, we don't have anything in/with Go on our server and after
returning back to 12.3 everything works normal.
--
You are receiving this mail because:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256507
d...@jetcafe.org changed:
What|Removed |Added
Summary|Apparent kernel memory leak |Apparent kernel memory leak
14 matches
Mail list logo
