BrowserContext shouldn't be deleted in single process mode
Bug #1297973 reported by
Chris Coulson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Oxide |
Fix Released
|
High
|
Chris Coulson | ||
Bug Description
In single process mode, there is a single RenderProcessHost and in-process RenderProcess that is never deleted until process shutdown. However, the BrowserContext that the RenderProcessHost is created with can be deleted, leaving the RenderProcessHost with a dangling pointer to it. This isn't possible in the default process mode because a RenderProcessHost is deleted once all RenderViewHost's and RenderFrameHost's are deleted, and we enforce that BrowserContext outlives these
| Changed in oxide: | |
| importance: | Undecided → High |
| status: | New → Triaged |
| Changed in oxide: | |
| milestone: | none → branch-1.3 |
| Changed in oxide: | |
| milestone: | branch-1.3 → branch-1.4 |
| Changed in oxide: | |
| status: | Triaged → In Progress |
| Changed in oxide: | |
| status: | In Progress → Fix Released |
| assignee: | nobody → Chris Coulson (chrisccoulson) |
To post a comment you must log in.
