Closed
Bug 1022586
Opened 11 years ago
Closed 11 years ago
[tarako only] kill the homescreen app when memory low, since Bug 1014272 - [tarako only] Run the homescreen in process
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Tracking
(blocking-b2g:1.3T+, b2g-v1.3 unaffected, b2g-v1.3T fixed, b2g-v1.4 unaffected, b2g-v2.0 unaffected, b2g-v2.1 unaffected)
RESOLVED
FIXED
blocking-b2g | 1.3T+ |
Tracking | Status | |
---|---|---|
b2g-v1.3 | --- | unaffected |
b2g-v1.3T | --- | fixed |
b2g-v1.4 | --- | unaffected |
b2g-v2.0 | --- | unaffected |
b2g-v2.1 | --- | unaffected |
People
(Reporter: ying.xu, Assigned: ying.xu)
References
Details
Attachments
(1 file, 2 obsolete files)
since Bug 1014272 - [tarako only] Run the homescreen in process.
homscreen app is launched in b2g process. that causes it can not be killed by LMK.
But we do need homescreen exited when running at background and memory low(receiving Memorypressure event) to free some memory for foreground apps(mostly, 3rd parties apps)
I think we should be careful not to kill homescreen too often, or else we defeat the purpose of bug 1014272.
![]() |
||
Updated•11 years ago
|
Flags: needinfo?(nhirata.bugzilla)
Comment 2•11 years ago
|
||
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #1)
> I think we should be careful not to kill homescreen too often, or else we
> defeat the purpose of bug 1014272.
Yes, we can kill it before foreground app killed, to pass top 3rd-party test case.
patch to kill homescreen
Please review
Attachment #8438930 -
Flags: review?(alive)
Comment 5•11 years ago
|
||
Comment on attachment 8438930 [details] [diff] [review]
kill-homscreen-onlowmemory.patch
Review of attachment 8438930 [details] [diff] [review]:
-----------------------------------------------------------------
Please do in homescreen_launcher and remove the dump.
More: you will end up adding many handlers if render() is called many times.
This kind of event listener should be in its manager not in instance level.
Attachment #8438930 -
Flags: review?(alive) → review-
![]() |
||
Updated•11 years ago
|
status-b2g-v1.3:
--- → unaffected
status-b2g-v1.3T:
--- → affected
status-b2g-v1.4:
--- → unaffected
status-b2g-v2.0:
--- → unaffected
status-b2g-v2.1:
--- → unaffected
Flags: needinfo?(nhirata.bugzilla)
![]() |
||
Updated•11 years ago
|
Flags: needinfo?(nhirata.bugzilla)
please review again
Attachment #8438930 -
Attachment is obsolete: true
Attachment #8440596 -
Flags: review?(alive)
Updated•11 years ago
|
Assignee: nobody → ying.xu
Comment 8•11 years ago
|
||
Attachment #8440596 -
Flags: review?(alive) → review+
Attachment #8440596 -
Attachment is obsolete: true
Assignee | ||
Comment 11•11 years ago
|
||
(In reply to Fabrice Desré [:fabrice] from comment #10)
> Ying, why did you flag me?
Oh, I wonder do you have any suggestions about this?
Updated•11 years ago
|
Attachment #8441963 -
Flags: review?(fabrice)
Comment 12•11 years ago
|
||
Ying, please set review? flag and add Fabrice.
Shrink more memory for foreground app with big memory usage.
Updated•11 years ago
|
Attachment #8441963 -
Flags: review?(alive)
Updated•11 years ago
|
Attachment #8441963 -
Flags: review?(fabrice)
Attachment #8441963 -
Flags: review?(alive)
Attachment #8441963 -
Flags: review+
Assignee | ||
Comment 13•11 years ago
|
||
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
![]() |
||
Updated•11 years ago
|
Flags: needinfo?(nhirata.bugzilla)
Comment 14•11 years ago
|
||
already landed on 1.3T, 1.3T+
blocking-b2g: 1.3T? → 1.3T+
Flags: needinfo?(jcheng)
Comment 15•11 years ago
|
||
Hi James, by yesterday's discussion, please help to update the result of monkey test about black homescreen issue and see if the issue related to homescreen was killed by memory pressure event.
Flags: needinfo?(james.zhang)
Updated•11 years ago
|
Comment 16•11 years ago
|
||
Danny, you can revert this commit and try to reproduce it. You don't need monkey test.
Flags: needinfo?(james.zhang)
Comment 17•11 years ago
|
||
(In reply to James Zhang (Spreadtrum) from comment #16)
> Danny, you can revert this commit and try to reproduce it. You don't need
> monkey test.
After revert below commit, I cannot reproduce the black homescreen issue.
commit 4ab1432ed292b306cf52d005a2b312ae5bc95d66
Author: ying.xu <ying.xu@spreadtrum.com>
Date: Mon Jun 16 17:10:19 2014 +0800
Bug#1022586 kill the homescreen app when memory low
[self test ] kill and restore ok
Comment 18•11 years ago
|
||
(In reply to Danny Liang [:dliang] from comment #17)
> (In reply to James Zhang (Spreadtrum) from comment #16)
> > Danny, you can revert this commit and try to reproduce it. You don't need
> > monkey test.
>
> After revert below commit, I cannot reproduce the black homescreen issue.
>
> commit 4ab1432ed292b306cf52d005a2b312ae5bc95d66
> Author: ying.xu <ying.xu@spreadtrum.com>
> Date: Mon Jun 16 17:10:19 2014 +0800
>
> Bug#1022586 kill the homescreen app when memory low
>
> [self test ] kill and restore ok
Hi,Danny
I think maybe it have some risk if the homescreen couldn't be killed.Once some issues occur in homescreen app, users have to recover the phone by restarting it.
Comment 19•11 years ago
|
||
(In reply to yang.zhao from comment #18)
> (In reply to Danny Liang [:dliang] from comment #17)
> > (In reply to James Zhang (Spreadtrum) from comment #16)
> > > Danny, you can revert this commit and try to reproduce it. You don't need
> > > monkey test.
> >
> > After revert below commit, I cannot reproduce the black homescreen issue.
> >
> > commit 4ab1432ed292b306cf52d005a2b312ae5bc95d66
> > Author: ying.xu <ying.xu@spreadtrum.com>
> > Date: Mon Jun 16 17:10:19 2014 +0800
> >
> > Bug#1022586 kill the homescreen app when memory low
> >
> > [self test ] kill and restore ok
> Hi,Danny
> I think maybe it have some risk if the homescreen couldn't be
> killed.Once some issues occur in homescreen app, users have to recover the
> phone by restarting it.
Without reverting the commit, switch application and wallpaper are black easily. By test on launch camera under background music, the black screen issue will be reproduced in 10 minutes.
That's why I recommend to revert it first.
You need to log in
before you can comment on or make changes to this bug.
Description
•