clelland
commented
3 weeks ago @noamr, can you take a look at this?
It's still a bit hand-wavy around definitions (what is a process, anyway? This spec doesn't seem like the place to define it) but it tries to explain the loose expectations about the relationships between document-controlling (renderer, in Chromium) and supervisor (browser) processes, that I expect we can find in any multi-process browser architecture.
It also better defines what to actually do when a crash is noticed, now that individual documents in the same origin can set different reporting endpoints.
Add a proper processing model for crash reporting.
This model defines the relationships between processes and documents, and defines a few conditions, such as out-of-memory and unresponsive. It covers what the user agent should do when it notices that a process has crashed for any reason, and which endpoints should receive reports.
Fixes: #11
:boom: Error: 500 Internal Server Error :boom:
PR Preview failed to build. (Last tried on Oct 25, 2024, 5:50 PM UTC).
More
PR Preview relies on a number of web services to run. There seems to be an issue with the following one: :rotating_light: [Spec Generator](https://www.w3.org/2015/labs/) - Spec Generator is the web service used to build specs that rely on ReSpec. :link: [Related URL]([object Object]) ``` 🕵️♀️ That doesn't seem to be a ReSpec document. Please check manually: http://localhost:8082/uploads/CwB9Hk/index.html?force=1&isPreview=true%3Fforce%3D1&isPreview=true&publishDate=2024-10-25 ``` _If you don't have enough information above to solve the error by yourself (or to understand to which web service the error is related to, if any), please [file an issue](https://github.com/tobie/pr-preview/issues/new?title=Error%20not%20surfaced%20properly&body=See%20WICG/crash-reporting%2319.)._