Skip to content

Cap pending LoAFs to avoid memory leak - #796

Merged
tunetheweb merged 3 commits into
mainfrom
cap-pending-loafs
Sep 14, 2026
Merged

tunetheweb merged 3 commits into
mainfrom
cap-pending-loafs

Conversation

@tunetheweb

Copy link
Copy Markdown
Member

Fixes #795

@tunetheweb
tunetheweb merged commit 2263928 into main Sep 14, 2026
14 checks passed
@tunetheweb
tunetheweb deleted the cap-pending-loafs branch September 14, 2026 22:43
@tunetheweb tunetheweb changed the title Cap pending loafs Cap pending LoAFs to avoid memory leak Sep 14, 2026
logaretm added a commit to getsentry/sentry-javascript that referenced this pull request Oct 5, 2026
We were on web-vitals 6.1.1, so I bumped it to the latest 6.2.3 to pick
up the upstream fixes.

**Changelog**

- Fixes an INP clean-up memory leak and caps pending LoAFs to avoid
another leak
([#799](GoogleChrome/web-vitals#799),
[#796](GoogleChrome/web-vitals#796))
- Fixes negative `resourceLoadDuration` in LCP attribution and negative
`inputDelay` in INP attribution
([#803](GoogleChrome/web-vitals#803),
[#789](GoogleChrome/web-vitals#789))
- Stops a spurious CLS report of 0 after a bfcache restore
([#786](GoogleChrome/web-vitals#786))
- Guards `supportedEntryTypes` for older browsers
([#787](GoogleChrome/web-vitals#787))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Memory leak in attribution/onINP.ts: pendingLoAFs accumulates unboundedly during long periods without user interaction

2 participants