Comment #8 on issue 7558 by yurkennis: If process priority set by user, Chrome shouldn't change it http://code.google.com/p/chromium/issues/detail?id=7558
> we can't really tell if the user manually changed priorities Just a reminder, it wasn't a Chrome user who changed summary to "...if priority set by user". Originally, it was just "Chrome changes its own process priority" [and it shouldn't]. It's very surprising that it's wontfixed. Noone can be sure that bugs like Issue 27380 (which currently takes 100% of CPU _all the time_) won't arise in future. As long as high CPU usage remains possible in future builds, please provide control over how it affects a user--by not changing priority by Chrome itself. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
