Closed
Bug 990975
Opened 10 years ago
Closed 10 years ago
[MTBF] Phone lost control and black background
Categories
(Firefox OS Graveyard :: Stability, defect)
Tracking
(b2g-v1.3 affected, b2g-v1.3T affected, b2g-v1.4 affected, b2g-v2.0 fixed, b2g-v2.1 fixed)
RESOLVED
DUPLICATE
of bug 1047645
People
(Reporter: wachen, Unassigned)
References
Details
Attachments
(1 file)
|
129.80 KB,
text/x-log
|
Details |
Adb is still on. Phone is still here. It's running under v1.3. I will get logcat and memory report upload later
|
Reporter | |
Comment 1•10 years ago
|
||
TEST RUN https://www.dropbox.com/s/9fg5qyzs9llkntl/mtbf_v130_mtbf1_13.test LOGCAT https://www.dropbox.com/s/p4za8cbci2op1fc/mtbf_v1.3_mtbf1_14.logcat MEMORY REPORT https://www.dropbox.com/s/u78y2hxlmsk35ak/about-memory-bug990975.tgz
|
|
Reporter | |
Comment 2•10 years ago
|
||
Hi, Brian and Kevin, I think this is a relatively important bug that I need dev to handle. Is there any possible that you people can get the right person to look at this issue?
Flags: needinfo?(khu)
Flags: needinfo?(brhuang)
|
||
Comment 4•10 years ago
|
||
logcat says https://github.com/mozilla-b2g/gaia/blob/v1.3/apps/system/js/lockscreen.js#L588 is wrong. It seems the active app reference is still there but the iframe is already removed.
|
||
Comment 5•10 years ago
|
||
Alive, do you know who can help to check this further?
Flags: needinfo?(brhuang) → needinfo?(alive)
|
|
Reporter | |
Comment 7•10 years ago
|
||
Kevin, test run info, logcat, and memory report is in comment 1. That's what I can provide as for now. However, the phone is still not dead yet. I think that should be enough. I will try to change the pref file of app manager and run it again...
|
|
Reporter | |
Comment 8•10 years ago
|
||
What kind of "more detailed information" do you need?
Flags: needinfo?(khu)
|
|
Reporter | |
Comment 10•10 years ago
|
||
This is actually running through MTBF, and there is no promise to reproduce a bug all the time. I can try, but there might be more bugs instead of reproducing this one only
|
|
Reporter | |
Comment 11•10 years ago
|
||
Hi, Kevin and Alive, I will try to rerun it several times. However, here is the thing, we seldom get a phone with adb connection still on. Usually, adb connection is disconnected. I will try to rerun it with preference settings so that Alive can look into it. Hi, Malini, Alan suspect this is not a B2G leaking, and this might be a marionette leaking. I have the memory report in comment 1. I myself also look through the memory report a little bit. This is increased by 43.25MB, and there are some marionette related issues might be in js-main-runtime. However, it's not that terrible though. 43.25 MB (100.0%) -- js-main-runtime ├──25.19 MB (58.24%) -- zones │ ├──21.11 MB (48.80%) ── unused-gc-things │ ├───3.92 MB (09.08%) -- strings │ │ ├──3.55 MB (08.21%) -- notable │ │ │ ├──1.26 MB (02.91%) ++ (21 tiny) │ │ │ ├──0.70 MB (01.61%) -- string(length=180749, copies=2, "{"from":"0","value":"<!DOCTYPE html>//n<html xmlns=//"http://www.w3.org/1999/xhtml//" lang=//"en-US//" dir=//"ltr//">(truncated)) │ │ │ │ ├──0.70 MB (01.61%) ── malloc-heap [+] │ │ │ │ └──0.00 MB (00.00%) ── gc-heap [+] │ │ │ ├──0.60 MB (01.38%) -- string(length=103659, copies=3, "{"from":"0","value":"(truncated)) │ │ │ │ ├──0.60 MB (01.38%) ── malloc-heap [+] │ │ │ │ └──0.00 MB (00.00%) ── gc-heap [+] │ │ │ ├──0.50 MB (01.16%) -- string(length=180874, copies=1, "1396363493481/tMarionette/tINFO/tsendToClient: {"from":"0","value":"<!DOCTYPE html>(truncated)) │ │ │ │ ├──0.50 MB (01.16%) ── malloc-heap [+] │ │ │ │ └──0.00 MB (00.00%) ── gc-heap [+] │ │ │ └──0.50 MB (01.16%) -- string(length=199452, copies=1, "199445:{"from":"0","value":"<!DOCTYPE html>(truncated)) │ │ │ ├──0.50 MB (01.16%) ── malloc-heap [+] │ │ │ └──0.00 MB (00.00%) ── gc-heap [+] │ │ └──0.37 MB (00.87%) ++ (2 tiny) │ └───0.16 MB (00.36%) ++ (5 tiny) ├──16.53 MB (38.23%) -- compartments │ ├──11.52 MB (26.64%) -- objects │ │ ├───9.15 MB (21.16%) -- gc-heap │ │ │ ├──4.91 MB (11.36%) ── ordinary │ │ │ ├──1.85 MB (04.28%) ── function │ │ │ ├──1.73 MB (03.99%) ── dense-array │ │ │ └──0.66 MB (01.53%) ── cross-compartment-wrapper │ │ └───2.37 MB (05.48%) -- malloc-heap │ │ ├──2.31 MB (05.34%) ── slots │ │ └──0.06 MB (00.14%) ++ (2 tiny) │ ├───3.72 MB (08.60%) -- shapes │ │ ├──2.09 MB (04.84%) -- malloc-heap │ │ │ ├──0.78 MB (01.80%) ── compartment-tables │ │ │ ├──0.67 MB (01.55%) ── tree-tables │ │ │ ├──0.51 MB (01.17%) ── dict-tables │ │ │ └──0.14 MB (00.33%) ── tree-shape-kids │ │ └──1.63 MB (03.76%) -- gc-heap │ │ ├──0.88 MB (02.04%) ── base │ │ ├──0.59 MB (01.37%) -- tree │ │ │ ├──0.47 MB (01.09%) ── global-parented │ │ │ └──0.12 MB (00.28%) ── non-global-parented │ │ └──0.15 MB (00.35%) ── dict │ ├───0.99 MB (02.28%) ── cross-compartment-wrapper-table │ └───0.30 MB (00.70%) ++ (4 tiny) ├───0.97 MB (02.23%) ── runtime └───0.56 MB (01.30%) ── gc-heap/chunk-admin 4 (100.0%) -- js-main-runtime-compartments ├──2 (50.00%) ── system/[System Principal], chrome://global/content/bindings/scrollbar.xml [3] └──2 (50.00%) -- user ├──3 (75.00%) ── app://system.gaiamobile.org/index.html, [anonymous sandbox] (from: chrome://marionette/content/marionette-listener.js:354) [3] [+] ├──-2 (-50.00%) ++ (4 tiny) └──1 (25.00%) ── moz-nullprincipal:{0632e0fb-e9d0-4f34-875a-69ec95ccf074} [+] However, comparing to that B2G along grew up 77.84 MB, I think that might not be the only concern we got here.
|
|
Reporter | |
Updated•10 years ago
|
Flags: needinfo?(mdas)
|
|
Reporter | |
Comment 12•10 years ago
|
||
|
|
Reporter | |
Comment 13•10 years ago
|
||
Malini, if you can work with alan to get more information, I will appreciate it. Alan, can you provide more information for malini to figure it out?
Flags: needinfo?(ahuang)
|
||
Comment 14•10 years ago
|
||
I'm looking at the about:memory logs, and it looks like the memory marionette is taking up is being reduced from about-memory-0 to about-memory-5, so I don't think that's the problem here, unless something crashed. Are there any crash logs?
Flags: needinfo?(mdas)
|
|
Reporter | |
Comment 15•10 years ago
|
||
No, there is no crash report since it didn't crashed. Alan, can you provide more information on this?
|
|
Reporter | |
Updated•10 years ago
|
Flags: needinfo?(ahuang)
|
|
Reporter | |
Comment 17•10 years ago
|
||
I used a bug in bugzilla to do multiple ni?, clean it up again
Flags: needinfo?(ahuang)
|
|
Reporter | |
Updated•10 years ago
|
Flags: needinfo?(ahuang)
|
||
Updated•10 years ago
|
Flags: needinfo?(alan.yenlin.huang)
|
|
Reporter | |
Updated•10 years ago
|
|
||
Updated•10 years ago
|
Component: Performance → MTBF
|
|
Reporter | |
Comment 18•10 years ago
|
||
It's not about MTBF framework. It should be stability category because there is nothing we can do in modifying MTBF
Component: MTBF → Stability
|
||
Comment 19•10 years ago
|
||
Looks to be another duplicate of bug 1047645. Can we please stop filing duplicates of the same issue?
|
|
||
Comment 20•10 years ago
|
||
Didn't notice that we filed this a long time ago :) Now that bug 1047645 has landed, this should be fixed as well in 2.0 and beyond.
Status: NEW → RESOLVED
Closed: 10 years ago
status-b2g-v1.3:
--- → affected
status-b2g-v1.3T:
--- → affected
status-b2g-v1.4:
--- → affected
status-b2g-v2.0:
--- → fixed
status-b2g-v2.1:
--- → fixed
Resolution: --- → FIXED
|
|
Reporter | |
Comment 21•10 years ago
|
||
It was a bug filed back almost 5 month ago with v1.3 running. We won't be able to verify it or so. Since no patch is commit in this bug, and it do look like the bug you mention. It should be dup to the bug you mentioned. After bug 1047645 verified fixed, this bug should be fine (verify after 1047645 verified.)
Flags: needinfo?(wachen)
Resolution: FIXED → DUPLICATE
|
|
Reporter | |
Comment 22•10 years ago
|
||
Just btw, all the same kind of bugs are filed before bug 1047645. No one wants to look into these MTBF bugs unless we have an urgent call from others (like QC or other companies). If anyone would look into this 4 months ago, there would be no urgent fixes required now. Moreover, things would be smoother. Anyway, thanks for reminder of this bug.
Flags: needinfo?(wachen)
|
|
Reporter | |
Updated•10 years ago
|
Flags: needinfo?(wachen)
(In reply to Walter Chen[:ypwalter][:wachen] from comment #22) > No one wants to look into these MTBF bugs unless we have an urgent call from > others (like QC or other companies). If anyone would look into this 4 months > ago, there would be no urgent fixes required now. Moreover, things would be > smoother. Yes, you're absolutely right. This is something that we desperately need to fix.
|
|
Reporter | |
Comment 24•10 years ago
|
||
Just a note here, this bug was found again after resolved dup by CAF. Don't jump to conclusion too fast in any cases. However, I am now going to cleared ni since it didn't reproduce in v2.1.
Flags: needinfo?(wachen)
|
||
Comment 25•10 years ago
|
||
Could you provide the detailed reproduce steps and video for me to verify this bug. Thanks.
Flags: needinfo?(wachen)
|
||
Comment 26•10 years ago
|
||
(In reply to Sue from comment #25) > Could you provide the detailed reproduce steps and video for me to verify > this bug. Thanks. This is MTBF (Mean time between failures) related issue, and it's executed by automation scripts. So skip this case by manual verification. Thank you.
Flags: needinfo?(wachen)
You need to log in
before you can comment on or make changes to this bug.
Description
•