(In reply to Andrew McCreight [:mccr8] from comment #4) > ... there are around 800 hangs with BackgroundHangManager::CollectCPUUsage() in the proto signature ... (Here's an example of a BackgroundHangManager::CollectCPUUsage() hang, which I assume is due to some OS function being slow: bp-0843cd24-eff9-48f1-9985-42aef0230217) What is interesting about those is that we end up inside `ZwQuerySystemInformation` which seems to be [deprecated since Windows 8](https://learn.microsoft.com/en-us/windows/win32/sysinfo/zwquerysysteminformation) but we get there through the [apparently non-deprecated `GetSystemTimes` function](https://learn.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-getsystemtimes). Not sure if it would be worth exploring if there are alternatives for that one, too?
Bug 1817498 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Andrew McCreight [:mccr8] from comment #4) > ... there are around 800 hangs with BackgroundHangManager::CollectCPUUsage() in the proto signature ... (Here's an example of a BackgroundHangManager::CollectCPUUsage() hang, which I assume is due to some OS function being slow: bp-0843cd24-eff9-48f1-9985-42aef0230217) What is interesting about those is that we end up inside `ZwQuerySystemInformation` which seems to be [deprecated since Windows 8](https://learn.microsoft.com/en-us/windows/win32/sysinfo/zwquerysysteminformation) but we get there through the [apparently non-deprecated `GetSystemTimes` function](https://learn.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-getsystemtimes). Not sure if it would be worth exploring if there are alternatives for that one, too? Edit: Errrh, the documentation says for `SYSTEM_PROCESSOR_PERFORMANCE_INFORMATION`: "Use GetSystemTimes instead to retrieve this information.". So probably nothing we can do here on our side?