Issue 2595: Main browser process hogs CPU and asks to close the wrong tab, negating the multi-process architecture http://code.google.com/p/chromium/issues/detail?id=2595
Comment #1 by dark0eternal: this problem is basically negating the theoretical advantages of the multi-process architecture, making it impossible to launch the task manager when the browser freezes, and can't check which renderer process is taking the most CPU since it's always the main browser process that hogs the CPU. -- 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 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
