Closed
Bug 1170898
Opened 9 years ago
Closed 7 years ago
[FirefoxOS_v2.1][dophin]Go to the Youku site, consuming CPU too high
Categories
(Firefox OS Graveyard :: Gaia::Browser, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: David.Zhao, Unassigned)
References
Details
Steps to reproduce: ---------------------------------------------------- Step 1: Open browser,and go www.youku.com; Step 2: Select one video and playing; Step 3: watch CPU consumption--KO result:CPU use almost 100%,and there Will appear the situation that app is killed,because of low memory Reproduce rate: 5/5
Dophin version: 7715ga: Gaia-Rev e4c6fee5a08daddf2d9dc90be7c1516e0f371f9d Gecko-Rev b0b3904715e39be3e9bce72fd15a442141c4e749 Build-ID 20150529152715 Version 34.0 Device-Name scx15_sp7715ga FW-Release 4.4.2 FW-Incremental 14 FW-Date Thu May 28 15:07:34 CST 2015 7715ea: Gaia-Rev e4c6fee5a08daddf2d9dc90be7c1516e0f371f9d Gecko-Rev b0b3904715e39be3e9bce72fd15a442141c4e749 Build-ID 20150527154309 Version 34.0 Device-Name scx15_sp7715ea FW-Release 4.4.2 FW-Incremental 222 FW-Date Wed May 27 15:39:07 CST 2015
Only playing video in youku site, the CPU info as follows: User 82%, System 15%, IOW 0%, IRQ 0% User 80 + Nice 91 + Sys 33 + Idle 1 + IOW 0 + IRQ 0 + SIRQ 2 = 207 PID PR CPU% S #THR VSS RSS PCY UID Name 2281 0 57% S 30 158340K 53936K fg u0_a2281 /system/b2g/b2g 107 0 35% S 63 224904K 48624K fg root /system/b2g/b2g 591 0 4% S 5 6008K 468K fg root /system/bin/slog 102 0 3% S 18 49140K 1816K fg media /system/bin/mediaserver 1803 0 1% R 1 1292K 304K fg root top User 79%, System 18%, IOW 0%, IRQ 0% User 94 + Nice 77 + Sys 40 + Idle 4 + IOW 0 + IRQ 0 + SIRQ 0 = 215 PID PR CPU% S #THR VSS RSS PCY UID Name 2281 0 45% R 30 158148K 53872K fg u0_a2281 /system/b2g/b2g 107 0 36% R 63 224712K 48640K fg root /system/b2g/b2g 102 0 5% S 18 49140K 1816K fg media /system/bin/mediaserver 591 0 5% S 5 6008K 468K fg root /system/bin/slog 2578 0 1% S 1 0K 0K fg root kworker/u2:4 User 81%, System 14%, IOW 0%, IRQ 0% User 107 + Nice 70 + Sys 31 + Idle 8 + IOW 0 + IRQ 0 + SIRQ 0 = 216 PID PR CPU% S #THR VSS RSS PCY UID Name 107 0 41% R 63 224864K 48676K fg root /system/b2g/b2g 2281 0 39% R 30 158300K 53648K fg u0_a2281 /system/b2g/b2g 591 0 6% S 5 6008K 468K fg root /system/bin/slog 102 0 5% S 18 49140K 1816K fg media /system/bin/mediaserver 1803 0 1% R 1 1292K 304K fg root top User 85%, System 12%, IOW 0%, IRQ 0% User 90 + Nice 94 + Sys 28 + Idle 4 + IOW 0 + IRQ 0 + SIRQ 0 = 216 PID PR CPU% S #THR VSS RSS PCY UID Name 2281 0 51% R 30 158340K 53656K fg u0_a2281 /system/b2g/b2g 107 0 33% R 63 224904K 48704K fg root /system/b2g/b2g 102 0 5% S 18 49140K 1820K fg media /system/bin/mediaserver 591 0 5% S 5 6008K 468K fg root /system/bin/slog 1803 0 1% R 1 1292K 304K fg root top
We compared using dophin and other Android phones to open the Youku website.We find Android phone open the web pages is through the optimization, with less resource occupied, but dophin open the Youku website is the same as Youku web pages in computer, with many resource loading
Hi Vance, please help to assign someone to investigate this bug, thanks
Flags: needinfo?(vchen)
Hi Kevin, Could you have a look with this bug, thanks
Flags: needinfo?(kevingrandon)
Hi Vincent, do you think you can help on this one? Also Zhaoyang, do you observe the same abnormal CPU consumption on Flame 2.1? Thanks
Flags: needinfo?(vliu)
Flags: needinfo?(vchen)
Flags: needinfo?(David.Zhao)
Hi Vance, Flame 2.1 performance is better than Dophin, but the use of Flame CPU will also very very high,when open a video in youku site Flame : User 75%, System 20%, IOW 0%, IRQ 4% User 110 + Nice 138 + Sys 67 + Idle 0 + IOW 0 + IRQ 0 + SIRQ 15 = 330 PID PR CPU% S #THR VSS RSS PCY UID Name 2089 0 41% R 19 136912K 83164K u0_a2089 /system/b2g/b2g 232 0 41% S 62 213168K 87092K root /system/b2g/b2g
Flags: needinfo?(David.Zhao)
Comment 8•9 years ago
|
||
I used the command |top -m 5 -d 1 -t| to profile CPU rate on Flame v2.1, It seems that Browser thread consumes the highest resource of CPU when playing a video in youku.com. PID TID PR CPU% S VSS RSS PCY UID Thread Proc 1494 1494 1 41% R 187388K 95816K u0_a1494 Browser /system/b2g/b2g 231 771 0 16% S 245448K 91108K root Compositor /system/b2g/b2g 3245 3245 0 5% R 1416K 656K root top top 1494 1495 1 1% S 187388K 95816K u0_a1494 Chrome_ChildThr /system/b2g/b2g 207 532 0 1% S 46340K 7584K fg media AudioOut_2 /system/bin/mediaserver I will have update if there is any further detailed information.
(In reply to Vincent Liu[:vliu] from comment #8) > I used the command |top -m 5 -d 1 -t| to profile CPU rate on Flame v2.1, It > seems that Browser thread consumes the highest resource of CPU when playing > a video in youku.com. > > > PID TID PR CPU% S VSS RSS PCY UID Thread Proc > 1494 1494 1 41% R 187388K 95816K u0_a1494 Browser > /system/b2g/b2g > 231 771 0 16% S 245448K 91108K root Compositor > /system/b2g/b2g > 3245 3245 0 5% R 1416K 656K root top top > 1494 1495 1 1% S 187388K 95816K u0_a1494 Chrome_ChildThr > /system/b2g/b2g > 207 532 0 1% S 46340K 7584K fg media AudioOut_2 > /system/bin/mediaserver > > I will have update if there is any further detailed information. Hi Vincent, I get the data of comment7,When flame is single core.Could you test again,When flame is single core.You can compare playing video in youku with playing video in youtube,you will find play video in youku consumes the much more resource of CPU. Thanks
Comment 10•9 years ago
|
||
When browser goes into youku, it keep repainting the full screen. This also consumes too much time to BuildDisplayList/PaintFrame. From the discussion with Chiajung, I'd verified that the WIP of Bug 1159997 to tight dirtyRegion to process displayList can actually reduce the CPU ratio. I would set proper flag for this bug.
Depends on: 1159997
Comment 11•9 years ago
|
||
There's unfortunately not too much I can do here. Seems like bug 1159997 might resolve this, and if not please set the flags here. Thanks!
Flags: needinfo?(kevingrandon)
Updated•8 years ago
|
Flags: needinfo?(vliu)
Comment 12•7 years ago
|
||
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.
Description
•