Closed Bug 990909 Opened 11 years ago Closed 8 years ago

[Memory Report] make memory report pull reports thread by thread or put files into sdcard

Categories

(Toolkit :: about:memory, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX
tracking-b2g backlog

People

(Reporter: wachen, Unassigned)

References

Details

If you just start the phone: In the beginning: Filesystem Size Used Free Blksize /data 161M 7M 153M 4096 In the end: Filesystem Size Used Free Blksize /data 161M 45M 115M 4096 However, if you ran the phone for awhile (like 12 hours), the free space might go down to as low as 70MB. I think this can be solved by pulling one thread and delete report of one thread. After that, the program continue to pull another thread. This could be a good temp solution. Maybe, try to dump that into memory card would be another solution?
Blocks: MTBF-Memory
We need better tooling to figure out how we can fix the memory issues.
blocking-b2g: --- → 1.3T?
agree but this will not be blocking the release, can we have QA or a-team continue working on this and uplift when we have the solution ready? thanks
blocking-b2g: 1.3T? → -
At the very least, we should backlog this.
blocking-b2g: - → backlog
I think Kyle Huey is helping on this issue! Thanks!
I can make it so that we grab GC/CC logs from processes individually rather than all at once. But this would be much simpler to solve by enlarging /data/local. Can you just put a bigger SD card in the device? That's a lot cheaper than spending engineering time on this ;-)
Component: Performance → about:memory
Flags: needinfo?(wachen)
Product: Firefox OS → Toolkit
Hi, Kyle, I just looked into it and I didn't find any difference when I insert/remove sd card by using df command. Is it possible for you to indicate how to allocate free space to /data/local?? Also, getting a bigger SD should be fine. I will try to see if I can get some more for all the devices once I know how to do so. Still, I have another concern. At the end, it will be running like 72 hours, a week, or so. The memory will finally get to a point that it bring down the device again or make the pulling or it really slow. Umm...anyway, waiting forward to your response first, and if it is possible, I will try to go for SD card method.
Flags: needinfo?(wachen)
So apparently the extra space from a bigger sdcard doesn't go to /data/local, but only /mnt/sdcard. Perhaps we should move the memory report writing to /mnt/sdcard?
Sounds reasonable to me.
Flags: needinfo?(n.nethercote)
Summary: [Memory Report] make memory report pull reports thread by thread → [Memory Report] make memory report pull reports thread by thread or put files into sdcard
Child processes can't write to /mnt/sdcard, but bug 973090 will make the parent process write all the reports.
Is this a problem in practice? If not, we should just close this bug.
We still doesn't have time to verify this. Please allow us some more time. Since there is no blocker set, can we just put this here for a little bit longer time. We would appreciate it.
Flags: needinfo?(wachen)
blocking-b2g: backlog → ---
This no longer seems important. Please reopen if you disagree.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Flags: needinfo?(wachen)
You need to log in before you can comment on or make changes to this bug.