Oxide

Oxide dumps GPUCache in current working directory if WebContext.dataPath isn't set

Bug #1430478 reported by Chris Coulson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Oxide
Fix Released
Undecided
Chris Coulson
Oxide branch-1.6

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)

Chris Coulson (chrisccoulson)
Changed in oxide:
milestone: none → branch-1.6
status: New → Fix Released
assignee: nobody → Chris Coulson (chrisccoulson)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.