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
The implementation of AppHangs has a few drawbacks, see #2715. The main problem is that non-fully blocking app hangs have random stacktraces, which aren't actionable. Ideally, we plan on linking such app hangs to profiles, but we haven't decided how to achieve this in the product. Until we decide, we can give the users an option to ignore non-fully blocking app hangs. Furthermore, we plan on adding support for the app hang rate, but for that we need to capture fatal app hangs first, which we currently don't do.
Still, we can do some improvements for AppHangs
The content you are editing has changed. Please copy your edits and refresh the page.
Description
The implementation of AppHangs has a few drawbacks, see #2715. The main problem is that non-fully blocking app hangs have random stacktraces, which aren't actionable. Ideally, we plan on linking such app hangs to profiles, but we haven't decided how to achieve this in the product. Until we decide, we can give the users an option to ignore non-fully blocking app hangs. Furthermore, we plan on adding support for the app hang rate, but for that we need to capture fatal app hangs first, which we currently don't do.
Still, we can do some improvements for AppHangs
Tasks
The text was updated successfully, but these errors were encountered: