Bun Event.prototype.timeStamp Returns 0 Regardless of Runtime Lifetime
Is it fixed? Not yet.
Ongoing since Nov 16, 22:35 UTC. First reported Nov 16, 22:35 UTC.
What happened
In Bun version 1.4.4+38afee6c8 and potentially other builds, Event.prototype.timeStamp always evaluates to 0 regardless of the runtime lifetime or when the event object is created. This affects scenarios like web servers and UI libraries where event timestamps are expected to reflect program uptime or performance. The issue is currently reported on Linux.
What caused it?
Under active investigation. No report has identified a root cause yet.
No verified workaround yet
None of the linked reports describe a mitigation. This page updates when one appears.
Timeline
- Investigating(current)
- Workaround available(upcoming)
- Resolved(upcoming)
- First report on GitHub issue
Event: Event.prototype.timeStamp is always 0 regardless of the runtime lifetime
Source
Evidence
1 report · 1 GitHubShow
- [1]GitHub First reportEvent: Event.prototype.timeStamp is always 0 regardless of the runtime lifetime(opens GitHub issue in a new tab)
What version of Bun is running? 1.4.4+38afee6c8 What platform is your computer? Linux 7.3.3-2-cachyos-eac x86_64 unknown What steps can reproduce the bug? Create a new event object on bun where the code is not immediately run. Example: webserver, node libraries that create a GUI where event after letting the program run, running a setInterval, creating an instance of an Event object will not set the program's lifetime. console.time("tick") setInterval(()=>{ console.log(performance.now())…
by by-moan 0upvotes 1comments
FAQ
What happened in the Bun issue?
In Bun version 1.4.4+38afee6c8 and potentially other builds, Event.prototype.timeStamp always evaluates to 0 regardless of the runtime lifetime or when the event object is created. This affects scenarios like web servers and UI libraries where event timestamps are expected to reflect program uptime or performance. The issue is currently reported on Linux.
What is affected by the Bun issue?
Bun (versions: 1.4.4+38afee6c8). Also affected at the same time: Linux.
When did the Bun issue start and end?
It started Nov 16, 22:35 UTC and is still ongoing (2 d 6 h so far). This page updates as it develops.
How do I get alerts for Bun?
Subscribe to the Bun RSS feed for every new Bun incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Bun is down. Bun feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.