"ExtensionApiTest.NativeMessagingBasic" is flaky |
||
Issue description"ExtensionApiTest.NativeMessagingBasic" is flaky. This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label. We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyMAsSBUZsYWtlIiVFeHRlbnNpb25BcGlUZXN0Lk5hdGl2ZU1lc3NhZ2luZ0Jhc2ljDA. Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs
,
May 24 2017
It appears that the problem is that the test gets error 1450 from RegCreateKeyEx(). 1450 is ERROR_NO_SYSTEM_RESOURCES. From https://support.microsoft.com/en-us/help/237304/fix-regopenkeyex-may-fail-with-status-1450 : On Windows NT 4.0 starting with Service Pack 4 (SP4), the key can be opened and closed only 65,535 times. Despite the error status code, no resource has been exhausted. Rather, an internal reference counter associated with the key has reached a limit. The reference counter is incremented when the key is opened but fails to be decremented when the key is closed. An application typically does not need to open and close this key so many times because the contents of this registry key do not change very frequently. This registry key only contains the titles and indexes of the counters, not the actual performance data. However, the problem is system-wide. This means that if Windows NT has been running for months, and a program runs many times an hour opening and closing this key, it is possible this error will occur. After the error occurs and RegOpenKeyEx can no longer open the key, no other processes can open the key either. At this time, the system must be restarted in order for an application to open the key again.
,
Dec 14 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by henrika@chromium.org
, May 12 2017Owner: sergeyu@chromium.org
Status: Assigned (was: Untriaged)