Virtual memory pointing value of namespace rather than pod

[human-77]

Description

I'm working with blockscout frontend, but the problem may be coming from prom-client.

Basically, I was creating some dashboards to monitor an instance of frontend running on a pod when I found this bizarre value for the virtual memory

# HELP frontend_process_virtual_memory_bytes Virtual memory size in bytes.
# TYPE frontend_process_virtual_memory_bytes gauge
frontend_process_virtual_memory_bytes 33012293632

Using kubectl describe ns my-namespace I got:

limits.memory                     9829Mi  30Gi
requests.cpu                      1800m   10
requests.ephemeral-storage        0       10Gi
requests.memory                   2560Mi  30Gi
requests.storage                  0       30Gi

In other words, despite running on a pod, the virtual memory is pointing the virtual memory of the WHOLE NAMESPACE.

I originally opened this issue on the blockscout frontend issues, however, they told me that the problem probably was on a bug on prom-client, more specifically, they believe is here.

Steps to reproduce

We are running it on a cloud using helm charts. I believe that you can simply run the pod on a namespace meant for multiple pods and the error should happen.

App version

v1.36.0

Operating system

Ubuntu docker image