Keep Running at Runtime

on YouTube ↗18m

" summary

Long-running web apps suffer different problems than page load; runtime focus targets errors, long tasks, frame rate, memory and throttling. Implement global error and unhandledrejection capture with a 100 ms debounce or use subscribable-things to avoid reimplementing it. Use ReportingObserver (Chrome) or CSP violation events for console-reported issues, and PerformanceObserver to detect long tasks (>~50 ms). Chrome supports async memory reads when the page is cross-origin-isolated (COOP/COEP headers). Use Wake Lock or worker/audio-based timers to avoid background throttling.

AI-written summary · about

" chapters (18)

1. 0:00Intro
2. 0:37Running story
3. 1:40Introduction
4. 2:27The fastest page
5. 3:36Track Runtime Errors
6. 4:44Track Runtime Rejections
7. 5:57Subcribable Things
8. 6:50Ignoring Errors
9. 7:38Reporting Observer
10. 8:38Servo
11. 9:53Tracking the Frame Rate
12. 11:58Tracking Memory Consumption
13. 13:44Memory Leak Prevention
14. 14:20JSF Profiling API
15. 14:45Lock Screen API
16. 15:46Timers
17. 16:42Conclusion
18. 17:35Outro

" related talks

• 50mWeb Performance APIs You (probably) Didn't Know ExistedMatheus Albuquerque · Build Stuff 2022
• 59mWeb performance APIs you (probably) didn't know existedMatheus Albuquerque · NDC Oslo 2022
• 01h 02mWeb Performance Tuning with browser APIsYaser Adel Mehraban · NDC London 2021
• 30mWeb runtime performanceMariko Kosaka, Jason Miller, Jake Archibald · Google I/O 2021
• 22mWeb Perf APIs That You (Probably) Never Knew ExistedMatheus Albuquerque · dotJS 2026
• 32mExpect the Unexpected: How to Deal with Errors in Large Web ApplicationsMats Bryntse · TestCon Vilnius 2018
• 55mI Feel the Need for Web Page SpeedBill Dinger · Build Stuff 2021
• 27mDon't block the event loop!JavaScript Async for Effortless UXJaeseok Kang · JSConf Korea 2019