Comment #1 on issue 27070 by Robert.Bradbury: Stopped plugin process hangs tab opens / Excess CPU time by Flash http://code.google.com/p/chromium/issues/detail?id=27070
The primary "flash" process, currently showing up on ps as "exe" because for some reason chromium appears to re-execute /proc/self/exe with the libflashplayer.so plugin. Not a bad thing just a different thing from the way other browsers approach flash. But there still exists the case that chromium is executing flash in an entirely controllable sub-process -- but it is failing to execute such management. So this leads to one of two conclusions (that the developers are paying no attention to the impact on the system that their children may have, or that they have implicitly agreed to let flash run wild and free). I have taken the step of stopping with "kill -s SIGSTOP `id of exe process`. And it does stop and CPU use is significantly reduced. I have also restarted this processes (kill -s SIGCONT `id of exe process` and it does continue. There is a period of intense CPU activiity -- largely associated with excessive numbers of futex() and gettimeofday() system calls on the part of FlashPlayer process(es). In short libflashplayer.so is not programmed to adjust to significant shifts in the "time-of-day" (i.e. you (as a program) have been sidelined for an extended period). The plug-in does appear to eventually catch up -- but it many take 20+ minutes of extensive CPU activity to do so. This is technically speaking a Flash bug -- Flashlibraries should accept and adapt to being Stoppped and Continued without imposing excessive processor requirements on the host. -- 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
