Closed Bug 1127757 Opened 10 years ago Closed 7 years ago

[Flame][Loop]When you invoke the loop call function, the CPU usage reaches 40%.

Categories

(Firefox OS Graveyard :: Gaia::Loop, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(tracking-b2g:backlog, b2g-v2.1 affected, b2g-v2.2 affected)

RESOLVED WONTFIX
tracking-b2g backlog
Tracking Status
b2g-v2.1 --- affected
b2g-v2.2 --- affected

People

(Reporter: liuke, Unassigned)

References

Details

Attachments

(4 files)

[1.Description]: According to 1104151, this bug is filed. [Flame 2.1 & 2.2][Market Custom Framework]When you use Loop to make a video call, the CPU usage reaches 40%. Found time: Flame 2.1: 3:16 Flame 2.2: 3:13 See attachment: Flame 2.1: Flame_21_system-info.txt and logcat_316.txt Flame 2.2: Flame_22_system-info.txt and logcat_313.txt [2.Testing Steps]: 1. Use USB to connect device with PC . 2. Launch Loop client app and establish video call between Flame 3. During video call, use "adb shell top -m 5" to check CPU usage. [3.Expected Result]: 3.When you use Loop call, the CPU usage should be rational. [4.Actual Result]: 3.The CPU usage reaches 40%. [5.Reproduction build]: Flame 2.1 version: Gaia-Rev 9df43e6e696da43b6a1433283dc5b155987747bc Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/095a46f32cd4 Build-ID 20150129003733 Version 34.0 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20150129.041104 FW-Date Thu Jan 29 04:11:14 EST 2015 Bootloader L1TC000118D0 Flame 2.2 version: Gaia-Rev 6e494f1d2676d231abba7dcc2e2822d1170d2d02 Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/5e6fac01a72f Build-ID 20150129003432 Version 37.0a2 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20150129.042943 FW-Date Thu Jan 29 04:29:53 EST 2015 Bootloader L1TC000118D0 [6.Reproduction Frequency]: Always Recurrence,5/5 [7.TCID]: Free Test
See Also: → 1104151
Attached file logcat_313.txt
Attached file logcat_316.txt
Depends on: 1104151
Oscar, can you have a look at it?
Flags: needinfo?(opatinobugzilla)
My first tests done on v2.1 and v2.2 verify that Hello on mobile is consuming that 40% cpu usage. Checking the different threads I couldn't see anything out of place: video encoding and decoding thread are at a low cpu usage and it seems that main Hello thread keeps relatively low 4%. I will try to dive into looking for performance issues capturing some profiles and viewing them in Cleopatra tool.
Flags: needinfo?(opatinobugzilla)
[Tracking Requested - why for this release]:
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: