Updates:
Status: WontFix
Comment #7 on issue 7558 by [email protected]: If process priority set
by user, Chrome shouldn't change it
http://code.google.com/p/chromium/issues/detail?id=7558
As noted earlier in the thread - we can't really tell if the user manually
changed
priorities.
I don't believe the issues raised by tconrad will be fixed by changing
priorities
anyway - the rtvscan problem is likely hung on disk IO - and the locked
after idle is
also not likely due to process priority.
I'm closing this bug as wontfix.
--
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
