Closed
Bug 1039445
Opened 10 years ago
Closed 10 years ago
[MTBF] homescreen not responding
Categories
(Firefox OS Graveyard :: Gaia::System::Window Mgmt, defect)
Tracking
(blocking-b2g:2.0+, b2g-v2.0 fixed, b2g-v2.1 fixed)
People
(Reporter: pyang, Assigned: etienne)
References
Details
(Whiteboard: [systemsfe])
Attachments
(4 files)
Device: flame
Memory: 273MB
Gaia 2c6c413ed729d465c52d6c2d5d458e2eee79e956
Gecko https://hg.mozilla.org/releases/mozilla-aurora/rev/d32649a24965
BuildID 20140715000201
Version 32.0a2
ro.build.version.incremental=109
ro.build.date=Mon Jun 16 16:51:29 CST 2014
STR:
Setup MTBF test
Test suite including keyboard, sms, music
Randomly run automation test cases for about 2~6 hours.
EXPECT: Homescreen can be showed correctly
ACTUAL: foreground app was still active. Homescreen completely blank
Reporter | ||
Comment 1•10 years ago
|
||
System tray is still working
Reporter | ||
Updated•10 years ago
|
Summary: [MTBF] Can switch to homescreen by home button → [MTBF] homescreen not responding
Reporter | ||
Comment 2•10 years ago
|
||
Add logcat
Updated•10 years ago
|
blocking-b2g: --- → 2.0?
Updated•10 years ago
|
Attachment #8456816 -
Attachment mime type: text/x-vhdl → text/plain
Comment 3•10 years ago
|
||
The output of b2g-ps would also be helpful.
Comment 4•10 years ago
|
||
One of the many homescreen issues which we will have to investigate given MTBF is <6hours ?
blocking-b2g: 2.0? → 2.0+
Component: General → Gaia::Homescreen
Flags: needinfo?(anygregor)
Maybe it's related to bug 1038136?
Updated•10 years ago
|
Updated•10 years ago
|
QA Whiteboard: [VH-FL-blocking-][VH-FC-blocking+] → [VH-FL-blocking-][VH-FC-blocking?]
Comment 6•10 years ago
|
||
This feels like either a system homescreen launcher bug, or a maybe another content parent issue.
Component: Gaia::Homescreen → Gaia::System::Window Mgmt
Reporter | ||
Comment 7•10 years ago
|
||
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #5)
> Maybe it's related to bug 1038136?
Not really because it didn't cause crash.
(In reply to Kevin Grandon :kgrandon from comment #6)
> This feels like either a system homescreen launcher bug, or a maybe another
> content parent issue.
Agree. And since symptom is diverse, please tell us what information could help.
Reporter | ||
Comment 8•10 years ago
|
||
Reproduce with build 201407160201
Gaia aa4f795b81c6147d67c4f06009e166debcf8856e
Gecko https://hg.mozilla.org/releases/mozilla-aurora/rev/0ec0b9ac39f0
BuildID 20140716160201
Version 32.0a2
ro.build.version.incremental=109
ro.build.date=Mon Jun 16 16:51:29 CST 2014
Assignee | ||
Comment 9•10 years ago
|
||
I can reproduce it, and it looks like a window management issue, having a look!
Assignee: nobody → etienne
Updated•10 years ago
|
Flags: needinfo?(anygregor)
Updated•10 years ago
|
Target Milestone: --- → 2.0 S6 (18july)
Assignee | ||
Comment 10•10 years ago
|
||
We had a race conditions where we dispatch |status-active| before the |attentionScreen.getBoundingClientRect().height| has been resized to status-mode (during the slide up transition), which made the layourManager.height computation to return 0.
So the height of the homescreenWindow was set to 0.
Attachment #8458648 -
Flags: review?(alive)
Comment 11•10 years ago
|
||
Comment on attachment 8458648 [details] [review]
Gaia PR
I guess I should close my eye and r+ because I don't need to care it anymore in 2.1
Attachment #8458648 -
Flags: review?(alive) → review+
Assignee | ||
Comment 12•10 years ago
|
||
Yep, this should be the last patch touching the attention screen without test :)
Assignee | ||
Comment 13•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 14•10 years ago
|
||
status-b2g-v2.0:
--- → fixed
status-b2g-v2.1:
--- → fixed
Reporter | ||
Comment 15•10 years ago
|
||
Great work Etienne!
You need to log in
before you can comment on or make changes to this bug.
Description
•