Metric timestamps in the distant past on chrome

[MisterSquishy]

What happened?

Steps to Reproduce

call createCounter('test_counter').add(1); from an instance of Chrome on version 106.0.5249.119 (i'm not sure exactly how far back this open bug goes, but it's definitely in that version)

Expected Result

test_counter metric emitted with timestamp reflecting the time the metric was recorded

Actual Result

test_counter metric emitted with timestamp from days/weeks ago, depending on how long you've had chrome open

Additional Details

this is the metrics side of #3355. both of these issues could be fixed by #3279, but it's actually even easier in the metrics case, since metrics don't need a monotonic clock and could safely just use Date.now()

OpenTelemetry Setup Code

No response

package.json

No response

Relevant log output

No response

[kidbai]

I had the same problem.
The npm what I use is "@opentelemetry/sdk-metrics": "^1.8.0",.
And the result is startTimeUnixNano":1671337155932700000,"timeUnixNano":1671337159934300000 which is generated just now but in the distant past.

[yuanman0109]

Is there any breakthrough in this issue