TaskManagerBrowserTest.IdleWakeups fails
Reported by
sabbaku...@yandex-team.ru,
May 3 2017
|
||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 YaBrowser/17.3.1.814 (beta) Yowser/2.5 Safari/537.36 Steps to reproduce the problem: Run the TaskManagerBrowserTest.IdleWakeups test. What is the expected behavior? What went wrong? On some Linux systems (like Ubuntu 14.04.5 or Ubuntu 16.04) with 4.8.0-49-generic kernel there's no /proc/<pid>/sched file. Or it exists but doesn't have the required se.statistics.nr_wakeups field. This causes TaskManagerBrowserTest.IdleWakeups test to fail and in Chrome Task Manager all the Idle Wakeups counts are 0. After some research I found out that the voluntary_ctxt_switches field in file /proc/<pid>/status is practically the same as the previous one. Using that field helps the test to pass. Did this work before? N/A Chrome version: 60.0.3088.0 Channel: n/a OS Version: Flash Version:
,
May 12 2017
,
May 30 2017
sabbakumov@ Could you please help us with the steps to verify this issue from TE-End. Thank You...
,
May 31 2017
kkaluri@ Sure. 1. Install Ubuntu 16.04 with the 4.8.0-49-generic kernel. 2. Open Chrome (before 93c0968c8188befdaeaf1d49a98ad9086fa4a0f3 commit, since I fixed the issue after that commit). 3. Open Chrome Task Manager. 4. Right click - select Idle Wakeups 5. Note that all wakeups count are 0. Also run the following command from the terminal: file /proc/1/sched The output of the command is: /proc/1/sched: cannot open `/proc/1/sched' (No such file or directory) That means the file Chrome uses for wakeups count is not available.
,
May 31 2017
Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 7 2017
Unable to reproduce the issue on Ubuntu 16.04 using chrome reported version #60.0.3088.0 . Attached a screen shot for reference. Following are the steps followed to reproduce the issue. ------------ 1. Opened chrome. 2. Opened Chrome Task Manager. 3. Right clicked and selected Idle Wakeups. 4. Observed that idle wakeups were non-zero. sabbakumov@ - Could you please check the screenshot and please let us know if anything missed from our side. Thanks...!!
,
Jun 8 2017
Do you use Chrome before my patch listed above? Also, what's your kernel version?
,
Jun 8 2017
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 29 2017
As per comment #7 tested in chrome Stable# 59.0.3071.115(Revision - 464641)before fix build with 4.4.0-79-generic on Ubuntu 14.04 & 16.04 and not able to reproduce the issue.Please find the screen shots for your reference. @Reporter:Could you please let me know if i have missed anything and if possible,Please create new profile without extensions and apps.Re-check once and let us know the observations of the issue which would help us to triage the issue further. Thanks in Advance.
,
Jul 10 2017
@ sabbakumov : Could you please update on comment #9.Which would help us to triage the issue further. Thanks in Advance.
,
Jul 11 2017
Could you please double check that you use 4.8.0-52-generic Linux kernel? Also instead of "file" command try to use: cat /proc/1/sched | grep se.statistics.nr_wakeups Just like in the Comment 7.
,
Jul 11 2017
Thank you for providing more feedback. Adding requester "rbasuvula@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 11 2017
Also please double check that you use Chrome before my patch listed above.
,
Jul 14 2017
Tested the issue on Linux Ubuntu 14.04 4.4.0-75-generic kernel using chrome version 60.0.3112.66 with the below steps 1. Opened chrome. 2. Opened Chrome Task Manager. 3. Right clicked and selected Idle Wakeups. 4. Observed that idle wakeups as like screenshot attached. 5. executed the command cat /proc/1/sched | grep se.statistics.nr_wakeups in terminal Please find the attached screen shot and confirm if anything missed here. attached screen shot of the issue on chrome version 60.0.3088.0 as well. Also please confirm is this issue specific to 4.8.0-52-generic Linux kernel? Thanks,
,
Jul 14 2017
It seems that all is right. Probably the issue is specific to the kernel settings.
,
Jul 14 2017
Thank you for providing more feedback. Adding requester "kavvaru@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 17 2017
Thanks for the update! Some one from "Task Manager" dev team please look in to this issue. Thank You!
,
Jul 18 2017
Adding TE-NeedsTriageFromMTV as the issue seems specific to 4.8.0-52-generic Linux kernel. MTV@ Could some one from MTV please check this issue if you have specific kernel. Thanks,
,
Jul 18
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by bugdroid1@chromium.org
, May 4 2017