You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a way to detect a particularly slow coroutine. It is always known that a coroutine should not block. However, once a project is complex enough, the chances of erroneous blocking of a coroutine are inevitable. I need a way to detect where asynchronous code is incorrectly introducing blocking. The detection criterion is that the execution time exceeds a certain value.
I hope this approach provides two pieces of information
Duration of the slow coroutine
Source code location of the slow coroutine
After some research, I found out that customizing an executor should enable the task of finding the slow coroutine to some extent. However, this approach makes it difficult to get information about the source location of the coroutine. Is there a better, less intrusive method?
The text was updated successfully, but these errors were encountered:
Is there a way to detect a particularly slow coroutine. It is always known that a coroutine should not block. However, once a project is complex enough, the chances of erroneous blocking of a coroutine are inevitable. I need a way to detect where asynchronous code is incorrectly introducing blocking. The detection criterion is that the execution time exceeds a certain value.
I hope this approach provides two pieces of information
After some research, I found out that customizing an executor should enable the task of finding the slow coroutine to some extent. However, this approach makes it difficult to get information about the source location of the coroutine. Is there a better, less intrusive method?
The text was updated successfully, but these errors were encountered: