Release 1.65.13
Release Notes - Seatmap Platform
Version 1.65.13 - 2026-05-15
Release Focus: Hotfix for the booking client — fix the venue background rendering tiny in the top-left of the viewport after the WebGL context is restored on mobile, reduce uncontrolled mobile context losses with a proactive teardown/restore path, and enrich Sentry diagnostics for any future occurrence.
What’s Fixed
Background image no longer renders tiny after WebGL context restore on mobile
Customers on mobile (iOS Safari, Facebook in-app browser, Android Chrome) intermittently saw the venue background collapse into a tiny image anchored at the top-left of the viewport after they returned to the tab or zoomed in/out following a period of inactivity. The seats and overlays were correct; only the background bitmap was wrong. Issue: SEAT-991.
What was happening
The browser silently kills the WebGL context on backgrounded or idle mobile tabs to reclaim GPU memory. When the context is restored, the renderer re-fetches the background image — but the restore path was assigning the new bitmap without normalising its dimensions to the venue’s viewBox. The shader quad ended up sized to the bitmap’s natural pixel dimensions (after 1.65.12, always the ~1000 px preview) instead of the venue’s coordinate space, so it rendered as a small image fixed at the venue’s top-left.
The mitigation introduced in 1.65.12 (SEAT-990) didn’t cause this regression but amplified it, because the restored background is now always the small preview rather than the full-resolution image.
What changed
- The context-restore path now applies the same viewBox dimension convention used by every other background load, so the quad matches the venue regardless of the bitmap’s natural pixel size.
- The booking renderer now proactively releases its GPU textures after the tab has been hidden for 30 s and restores them deterministically when the tab is foregrounded again. This reduces the rate of uncontrolled browser-initiated context losses on mobile.
webglcontextlostevents captured in Sentry now include richer diagnostic context (visibility state, session age, devicePixelRatio, GPU capability tier, background-image source / dimensions / estimated VRAM cost, and live state flags) so the next occurrence can be triaged without guessing.
Who benefits
Any customer running the booking renderer on a mobile or in-app-browser environment, especially on flows where the user may leave the tab and return (checkout, gallery, multi-tab booking).
Migration
None — drop-in patch release.
Affected products
booking-client— fix inWebGLLayer.ts; regression tests added inWebGLLayer.contextLoss.test.ts.
Upgrade
npm install @seatmap.pro/renderer@1.65.13
No API or configuration changes.