datamuc

I have a similar thing, but we are on 0.15: The go_memstat* things look pretty normal to me: go_memstats.*bytes are very constant during the week:  go_memstats_alloc_bytes and frees_total: ...

It doesn't happen on every machine, but if it happens it seems to be the service collector that is leaking memory. In general the windows_exporter is leaking memory anyways, it's...

> Unfortunately the heap dumps aren't too helpful: they're showing similar results to the `go_memstats_alloc_bytes_total` metric. @datamuc I wasn't able to view the dumps you provided, could you re-generate and...

> Hmm, those heap dumps are similar to those submitted earlier, with only a few MB allocated 😞 > > @datamuc from previous comments, it appears the `service` collector may...

The config: ```yaml log: level: fatal collectors: enabled: "process" collector: process: whitelist: "windows_exporter|exporter_exporter" blacklist: "" ``` And I did run this powershell script for an hour or so: ```powershell while($true)...

I've did some more testing. If I only enable the textfile exporter, then there is no leak. I tried to investigate a bit. I've seen that the windows_exporter uses a...

Does anybody have an idea? We are considering to move to telegraf and scrape that for the windows metrics.

@carlpett I've added the mentioned line and compiled a binary. The change didn't help anything regarding the leak. :disappointed:

What do you think? Should we try to bring this issue up in the [Prometheus & The Ecosystem Community Meeting](https://github.com/prometheus-community/community)? Maybe sombody there can help or knows somebody who can...

> Are we able to confirm if the excessive memory consumption occurs when disabling all collectors that use WMI as a metric source? These are currently cpu_info, fsrmquota, msmq, mssql,...