Public bug reported: If WebContext.dataPath and WebContext.cachePath aren't set, in memory storage should just be used for everything in the same way it is for incognito mode. However, Chromium currently dumps a GPUCache folder in the current working directory.
Rather than fix this, we should probably just disable it entirely (see https://code.google.com/p/chromium/issues/detail?id=249739) ** Affects: oxide Importance: Undecided 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/1430478 Title: Oxide dumps GPUCache in current working directory if WebContext.dataPath isn't set Status in Oxide Webview: Fix Released Bug description: If WebContext.dataPath and WebContext.cachePath aren't set, in memory storage should just be used for everything in the same way it is for incognito mode. However, Chromium currently dumps a GPUCache folder in the current working directory. Rather than fix this, we should probably just disable it entirely (see https://code.google.com/p/chromium/issues/detail?id=249739) To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1430478/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
