FreeBSD: couldn't get uname: cannot allocate memory

Host operating system: output of uname -a

FreeBSD XXXX 14.0-CURRENT FreeBSD 14.0-CURRENT #1 RELENG_2_7_0-n255866-686c8d3c1f0: Wed Jun 28 04:21:19 UTC 2023     root@freebsd:/var/jenkins/workspace/pfSense-CE-snapshots-2_7_0-main/obj/amd64/LwYAddCr/var/jenkins/workspace/pfSense-CE-snapshots-2_7_0-main/sources/FreeBSD-src-RELENG_2_7_0/amd64.amd64/sys/pfSense amd64

node_exporter version: output of node_exporter --version

node_exporter, version 1.5.0 (branch: release-1.5, revision: 5)
  build user:       nobody
  build date:       
  go version:       go1.20.3
  platform:         freebsd/amd64

node_exporter command line flags

/usr/local/bin/node_exporter --web.listen-address=192.168.192.1:9100 --collector.textfile.directory=/var/tmp/node_exporter --collector.boottime --collector.cpu --collector.exec --collector.filesystem --collector.loadavg --collector.meminfo --collector.netdev --collector.textfile --collector.time --log.level=warn

node_exporter log output

s=2023-09-22T20:05:32.809Z caller=collector.go:169 level=error msg="collector failed" name=uname duration_seconds=0.000157114 err="cannot allocate memory" 

Are you running node_exporter in Docker?

No

What did you do that produced an error?

Run node_exporter.

What did you expect to see?

node_uname_info metric.

What did you see instead?

node_scrape_collector_success{collector="uname"} 0

Reproduce the failure by running node_exporter 1.5.0 on FreeBSD 14.0-CURRENT with the reported flags, then trace the uname collector named in the log. Compare the collector error path with the expected node_uname_info metric; done means the collector succeeds or the allocation failure is clearly diagnosed and handled.