Dashboard auto-refresh causes browser memory to grow until a crash Planned
Planned: Scoped for the next release.
Claim the Metabase page
Claiming is free. You prove you work at Metabase with an email address at metabase.com; Friction sends a link there.
- 111 reports from users of Metabase
- 111 separate source threads
- 2015–2026 the years they cover
- Most recurring theme: High memory use under sustained workloads, 3 threads
These are public today, under your product's name. A reply from Metabase sits under the report, on the record, marked as verified at metabase.com: the next person who reads it sees you answered.
What Metabase would post on the top report
Built on the report people repeat most on this page. Nothing appears until you post it.
A first reply, under the report
A board post, with a public status
A changelog entry, linked to the report
Fixed: Dashboard auto-refresh causes browser memory to grow until a crash
Resolves: Dashboard auto-refresh causes browser memory to grow until a crash
Reports are not edited or removed by the vendor; a wrong one is flagged and reviewed within 3 working days. More on what vendors get.