Use AsyncTask#executeOnExecutor() instead of execute(). |
||||
Issue descriptionAsyncTask#execute() doesn't execute the tasks on a thread pool but on a single background thread, leading to potential queuing, since AsyncTasks are typically used for long-running background operations. Chrome has a lot of these calls, and most of them should be able to run on the concurrent executor. For the other ones, documenting that the serial executor is needed is better. See https://cs.chromium.org/chromium/src/chrome/android/java/src/org/chromium/chrome/browser/share/ShareHelper.java?q=%22.execute()%22+lang:java&sq=package:chromium&l=272&dr=C One such instance is in ShareHelper.
,
May 1 2017
,
May 2 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 7
This regression has been open for half a year. It's not very actionable and the regression has been in all Chrome user's hands for months. |
||||
►
Sign in to add a comment |
||||
Comment 1 by tedc...@chromium.org
, Nov 15 2016