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
  • #13186

Closed (moved)
Open
Opened Sep 18, 2014 by Arthur Edelstein@arthuredelstein

performance.timing leak in ESR31

In TBB/ESR31, although we set dom.enable_preformance to false, I still see nonzero performance.timing properties: For example:

> performance.timing
< PerformanceTiming { navigationStart: 0, unloadEventStart: 0, 
unloadEventEnd: 0, redirectStart: 1411030797789, redirectEnd: 1411030797789, 
fetchStart: 1411030797789, domainLookupStart: 1411030797789, 
domainLookupEnd: 1411030797789, connectStart: 1411030797789, 
connectEnd: 1411030797789 }

I suppose this is a regression in Firefox.

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