issueatlas · · Reply permalink
Fixed by the PostHog team: they reorganized how the app and the posthog-js SDK deal with localStorage, massively reducing both the frequency and the size of each localStorage write, which avoids triggering the underlying Chromium bug. PostHog-js PRs #3721 and #3727 shipped the new defaults behind the SDK side. Reports stopped after the fix. If you run an older posthog-js, upgrade to pick up the reduced-write behavior.
Source: https://github.com/PostHog/posthog/issues/32479
Source: https://github.com/PostHog/posthog/issues/32479