Closed Bug 915073 Opened 11 years ago Closed 11 years ago

[1.2] Contacts App launch time has regressed (compared to [1.1])

Categories

(Firefox OS Graveyard :: Gaia::Contacts, defect, P1)

All
Gonk (Firefox OS)
defect

Tracking

(blocking-b2g:koi+)

RESOLVED DUPLICATE of bug 914913
blocking-b2g koi+

People

(Reporter: mvikram, Assigned: bkelly)

References

Details

(Keywords: perf, regression, Whiteboard: [c=progress p= s= u=1.2] )

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.66 Safari/537.36 Steps to reproduce: Launch the Contacts App (QRD 7x27 device). Measurements are made using a high speed camera measuring the time from when the touch event was recognized to first app paint. Actual results: Measured time on (1.2) is: 3317 ms Measured time on (1.1): 2119 ms Expected results: Would expect launch time to be close to 1.1 or better.
Depends on: 914913
OS: All → Gonk (Firefox OS)
Priority: -- → P1
blocking-b2g: --- → koi+
Keywords: perf
Whiteboard: [c=progress p= s= u=1.2]
Depends on: 907907
This seems like a dupe of bug 914913. Does anyone object to consolidating this under that other bug?
Assignee: nobody → bkelly
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Nope, just carry over the "regression" keyword and Vikram's reported numbers to bug 914913 when you close this one: (In reply to Mandyam Vikram from comment #0) > User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, > like Gecko) Chrome/29.0.1547.66 Safari/537.36 > > Steps to reproduce: > > Launch the Contacts App (QRD 7x27 device). Measurements are made using a > high speed camera measuring the time from when the touch event was > recognized to first app paint. > > > Actual results: > > Measured time on (1.2) is: > 3317 ms > Measured time on (1.1): > 2119 ms > > > Expected results: > > Would expect launch time to be close to 1.1 or better.
Keywords: regression
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
No longer depends on: 914913
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.