ubuntu-webapps-bugs team mailing list archive

[Chris Coulson <chrisccoulson@xxxxxxxxxx>]

Public bug reported:

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.

** Affects: oxide
     Importance: High
     Assignee: Chris Coulson (chrisccoulson)
         Status: Fix Released

-- 
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