Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #22451

Closed (moved)
Open
Opened May 30, 2017 by Georg Koppen@gk

about:cache is not useful anymore in ESR52-based Tor Browser (only wyciwyg-URIs if at all any)

I wanted to investigate #21689 (moved) and started to look at about:cache output to check for isolation keys. But to my surprise there is only garbage in it (in e10s mode), meaning all URLs start with the wyciwyg scheme, or nothing at all (in non-e10s-mode).

After re-reading #9336 (moved) I suspect the cached elements are basically not showing up in e10s mode either but instead some weird wyciwyg incarnations.

Now, I tested manually that things are still cached and that cache isolation seems to be working which is a good thing. But we should investigate and fix this issue as it is highly confusing and might conceal bugs we would otherwise see.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#22451