2 people reported
All time, since Sep 29.
process.hrtime starts near zero
“process.hrtime.bigint() (and process.hrtime()) inside a Worker counts from that worker's own start rather than from the origin the main thread uses.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/bun/issues/4750/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
process.hrtime counts from process or worker start, not system clock. Readings start near zero, so values from Workers, other processes or CLOCK_MONOTONIC tools can't be compared as in Node.
Is this your bug?
File my report- Where
- process.hrtime
- Versions
- 1.4.2 to 1.4.3-canary.1
- Platforms
- Linux
- How bad
- Breaks a normal workflow.