feat(perf): track js heap size on canvas context loss and dashboard load

[thmsobrmlr]

Problem

I suspect that canvas elements lose their context due to OOMing for a customer: #28379.

Changes

This PR uses Chromiums's non-standard memory extension to capture heap usage after each dashboard load and when a canvas context loss is detected. I'm hoping to confirm/reject the OOM hypothesis for the customer issue with this.

How did you test this code?

Ran locally

[greptile-apps]

PR Summary

Added JavaScript heap memory tracking to diagnose potential out-of-memory issues causing canvas context loss in dashboards and visualizations.

• Added memory metrics collection in /frontend/src/scenes/dashboard/dashboardLogic.tsx during dashboard loads and time-to-see-data reporting
• Implemented getJSHeapMemory() utility in /frontend/src/lib/utils.tsx to capture heap usage metrics using Chrome's performance.memory API
• Added memory tracking in /frontend/src/scenes/insights/views/LineGraph/LineGraph.tsx when canvas context loss events occur
• Memory tracking is non-intrusive and gracefully handles browsers without the performance.memory API

_{3 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings | Greptile}

[github-actions]

Size Change: 0 B

Total Size: 1.18 MB

ℹ️ View Unchanged

Filename	Size
frontend/dist/toolbar.js	1.18 MB

_{compressed-size-action}

[aspicer]

✅ to unblock if you think this is worthwhile, but as i mentioned on slack, this crashes on my machine and doesn't seem to be memory limited.

seems to be a bug in GPU rendering in chrome.