Share via

Hundreds of asynchronous operations every second in 2 of my PCs

Jakeeer 15 Reputation points
2024-03-31T02:46:31.39+00:00

When I enabling logging in event viewer for AsyncCausality this is what I see, immediately:

4112 Event fired when an asynchronous operation is created.

8208 Event fired when an asynchronous operation is completed.

16400 Event fired when a synchronous work item starts.

20496 Event fired when a synchronous work item completes.

4112 Event fired when an asynchronous operation is created.

Over 100 of these per second. After a minute or so the log stops recording them because it's too full.

At least one other machine in my home gets these same events at the same frequency as well.

The PID listed in the details pane varies. Normally when I check task manager there's nothing matching it but one time it was the PID for Gaming Services IIRC.

a1

a2

A3

A4 Is this indicative of my PC having a performance problem? Because every PC in my home has an elusive issue with online games having frametime spikes and desync intermittently, that happen across different version of Windows, different hardware configurations, different ISPs, fresh installs of Windows, clean boot, etc. I've been trying to fix it for a while but I'm starting to really think it's something environmental causing it, or possibly it's just in my head.

I'm curious if anyone could try enabling logging for AsyncCausality and telling me if they get the same critical errors I do.

Windows 10 Home19045.4170

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
11,006 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ian Xue (Shanghai Wicresoft Co., Ltd.) 32,336 Reputation points Microsoft Vendor
    2024-04-02T06:35:04.1266667+00:00

    Hi Jakeeer,

    Thanks for your post. Generally speaking, With the advent of C# 5, Visual Basic .NET 11, the Microsoft .NET Framework 4.5 and .NET for Windows Store apps, the asynchronous programming experience has been streamlined greatly. New async and await keywords (Async and Await in Visual Basic) allow developers to maintain the same abstraction they were used to when writing synchronous code.

    A lot of effort was put into Visual Studio 2012 to improve asynchronous debugging with tools such as Parallel Stacks, Parallel Tasks, Parallel Watch and the Concurrency Visualizer. However, in terms of being on par with the synchronous code debugging experience, we’re not quite there yet.

    One of the more prominent issues that breaks the abstraction and reveals internal plumbing behind the async/await façade is the lack of call stack information in the debugger. In this article, I’m going to provide means to bridge this gap and improve the asynchronous debugging experience in your .NET 4.5 or Windows Store app.

    Reference: Async Programming - Async Causality Chain Tracking | Microsoft Learn

    Best Regards,

    Ian Xue

    If the Answer is helpful, please click "Accept Answer" and upvote it.