TPEPerformance/Meetings/2016-10-17

From MozillaWiki
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.


« previous week | index | next week »

OKR confidence

  1. O: Make Firefox more stable [current crash rates] [Crashes per 1000 usage hours]
    1. KR: 1.2 nightly browser crashes per 100 ADI (per-month median)
      • Current: 2.46 -> 3.21 -> 2.38 -> n/a -> 1.65 -> 2.83 -> 2.58
    2. KR: 0.3 nightly startup crashes per 100 ADI (per-month median)
      • Current: 0.81 -> 0.82 -> 0.72 -> n/a -> 0.6 -> 0.91 -> 0.83
    3. KR: 2.0 nightly content crashes per 100 ADI (per-month median)
      • Current: 14.38 -> 8.70 -> 8.25 -> n/a -> 7.19 -> 10.91 -> 8.90
  2. O: Improve Google document performance on Firefox
    1. O: Understand Google document performance issues on Firefox
      1. KR: Implement proposed fixes and measure results
        • Current:

Health Checks

  1. Test code coverage (minus crash/no return code path)
    • N/A
  2. Team mental health
    • Good
  3. ADI / DAU / MAU
    • N/A

Previous Week

gweng

  • analysing Ion threads after NIed others; mainly for weekly productivity, don't know if it can benefit our performance project yet

kanru

cervantes

  • discussed with Bevis Tseng about runnable labeling and scheduling
  • bug 1289994 - Use Application Verifier
    • running app verifier with 4,5,6 among 11 mochitest chunks
    • running app verifier with 2,3/11 mochites suite.
    • running jsapi-tests and reftest with app verifier
    • running app verifier with 1/11 mochitest suite
  • bug 1310152 - NEW [App Verifier] Critical section not initialized in sqlite3
  • bug 1309840 - RESOLVED::INVALID [App Verifier] js::ConditionVariable initializes a SRW lock that is already initialized
    • close as invalid since it's a false alarm cause by poisoning in malloc
  • bug 1308423 - NEW [App Verifier] Critical section not initialized in cubeb
    • updating the patch on upstream
    • landed in upstream

thinker

  • TODO: fixed size elements and it's children should be reflowed in parallel.
  • HTML parser would be blocked by JS blocks for document.write(), but we can stop blocking by merging content generated by document.write(), and redoing prasing if there is confliction.

wcpan

  • bug 1310127 NEW Use MOZ_MUST_USE in netwerk/protocol/http

ting

  • triaged 1009 nightly crashes
  • bug 1299747 - RESOLVED FIXED Create a tool to track 64k unaligned virtual memory allocation
    • implemented code to hook also the spawned content process, however the log doesn't appear, am investigating
    • fixed the logs from child process and added a batch file for easier usage, closed.
  • bug 1293501 - NEW Add debug annotation/code for the crash in ReleaseData()
    • pushed the patch of using VirtualProtect to protect mData to inbound

This Week Priorities

gweng

  • Trace JS compilation.
  • Persuade JS peers to reply their needinfo.

kanru

  • Sort out test coverage framework

cervantes

  • Run remaining tests with App verifier
  • Look at coverity

thinker

  • SVG blur test cases & fix harness
  • Study performance related documents

wcpan

  • MOZ_MUST_USE in network/protocol/
  • Coverity

ting

  • Use memory tool to find problems

Incoming

  • Oct: Oct-21 some team memebres will go on a two weeks around-the-island bike trip
  • Nov: WebSummit/CodeSummit