| Thread Previous • Date Previous • Date Next • Thread Next |
https://git.launchpad.net/oxide/commit/?id=02e9b3b9a0e6ca7076fa32f89447db88b19deb26
** Changed in: oxide
Importance: Undecided => High
** Changed in: oxide
Status: New => Fix Released
** Changed in: oxide
Milestone: None => branch-1.22
** Changed in: oxide
Assignee: (unassigned) => Chris Coulson (chrisccoulson)
--
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1663609
Title:
Leak BrowserProcessMain at shutdown
Status in Oxide:
Fix Released
Bug description:
We currently run the BrowserProcessMain destructor at process exit,
but this results in a CHECK failure in the event of an unclean
shutdown (ie, anything outside of Oxide just calling exit()).
See, eg, bug 1560994 and bug 1649262 - both bugs originally reported
against Oxide but are actually nothing to do with it.
Given that most singletons in Chromium are already leaky, we should
probably just leak this too.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1663609/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |
