Closed
Bug 975967
Opened 10 years ago
Closed 10 years ago
[tarako][fugu][buri][settings] settings screen show a white part when user quickly swipe
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 942750
People
(Reporter: angelc04, Unassigned)
Details
Attachments
(1 file)
732 bytes,
patch
|
Details | Diff | Splinter Review |
STR: 1. Kill Settings app 2. Launch Gallery/Music/Video to make device performance is slow 3. Launch Settings 4. Quickly swipe settings --> There is always a white part shows especially when device performance is bad. Please see STR video: https://mozilla.box.com/s/8p8a71tgqcf2m096rwz0 Build ID: 20140220161736
Reporter | ||
Comment 1•10 years ago
|
||
(In reply to pcheng from comment #0) > STR: > 1. Kill Settings app > 2. Launch Gallery/Music/Video to make device performance is slow > 3. Launch Settings > 4. Quickly swipe settings > --> There is always a white part shows especially when device performance > is bad. > > Please see STR video: https://mozilla.box.com/s/8p8a71tgqcf2m096rwz0 > > Build ID: 20140220161736 This build id is for Tarako. Fugu and Buri also have the same problem. But since the performance are better than tarako, it's hard to notice this problem.
Summary: [tarako][fugu][settings] settings screen show a white part when user quickly swipe → [tarako][fugu][buri][settings] settings screen show a white part when user quickly swipe
Comment 2•10 years ago
|
||
buri/tarako/fugu also have this issue.
blocking-b2g: --- → 1.3T?
Flags: needinfo?(ttsai)
not only setting app had this problem. sms contact calllog, they all have this problem and not related with system memery(256M/128M). make reference-workload-heavy and slide quickly,you'll see the bug I noticed that all the apps having this problem involved the list label. Hope useful.
Comment 4•10 years ago
|
||
(In reply to ying.xu from comment #3) > not only setting app had this problem. > > sms contact calllog, they all have this problem and not related with system > memery(256M/128M). > > make reference-workload-heavy and slide quickly,you'll see the bug > > I noticed that all the apps having this problem involved the list label. > Hope useful. So it's general issue.
Component: Gaia::Settings → General
Updated•10 years ago
|
Flags: needinfo?(ttsai)
Comment 5•10 years ago
|
||
Any enhancing plan or is this a known limitation?
Flags: needinfo?(tlee)
Flags: needinfo?(pchang)
Comment 6•10 years ago
|
||
It is very likely to be an issue of APZ. What do you think kats?
Flags: needinfo?(tlee) → needinfo?(bugmail.mozilla)
Comment 7•10 years ago
|
||
This looks like standard checkerboarding.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(bugmail.mozilla)
Resolution: --- → DUPLICATE
Updated•10 years ago
|
blocking-b2g: 1.3T? → ---
Updated•10 years ago
|
Flags: needinfo?(pchang)
Comment 8•10 years ago
|
||
We need disable APZC on v1.3t branch or cherry-pick v1.4 patch to v1.3t.
Flags: needinfo?(ttsai)
Flags: needinfo?(styang)
Updated•10 years ago
|
Flags: needinfo?(ttsai) → needinfo?(vliu)
Updated•10 years ago
|
Flags: needinfo?(styang)
Comment 9•10 years ago
|
||
(In reply to James Zhang from comment #8) > We need disable APZC on v1.3t branch or cherry-pick v1.4 patch to v1.3t. Patch to disable APZE is attached. With APZC, the preformance for quickly wiping is better than disabling it. It is resonable because the panning and zooming to be performed on the compositor thread rather than the main thead. We can still look forward to the land of bug 942750.
Flags: needinfo?(vliu)
Comment 10•10 years ago
|
||
(In reply to Vincent Liu[:vliu] from comment #9) > Patch to disable APZE is attached. With APZC, the preformance for quickly > wiping is better than disabling it. It is resonable because the panning and > zooming to be performed on the compositor thread rather than the main thead. Does it mean more memory consuming?
Comment 11•10 years ago
|
||
We have seen less memory usage with apz in most cases. We should really not disable it.
Comment 12•10 years ago
|
||
I think we should fix it on v1.3t, the reproduce rate is 100%.
blocking-b2g: --- → 1.3T?
Updated•10 years ago
|
blocking-b2g: 1.3T? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•