I can't kill a chrome process that has become unresponsive2 Recommended Answers
taskkill /F /FI "IMAGENAME eq chrome*"
After debugging this issue for days, I found the culprit in my case--McAfee Host Intrusion Prevention. McAfee creates intermediate filter drivers that appear as devices in device manager under "Network Interfaces." By temporarily disabling the McAfee HIPS program, the Chrome process that was stuck in the "Wait:Executive" state was immediately terminated.
It is possible that in other people's cases, it may not be McAfee in particular, but it is likely caused by some kind of intermediate network filter. Check for Host Intrusion Prevention, Firewall, and Anti-Virus services. Try disabling them and see if the unkillable processes come back from being zombies.
Again, I can't guarantee that this will work in every case, but I am just so happy to not have to restart my computer every 15 minutes because I have a unkillable Chrome process hanging onto 200MB of RAM!
A thread of the parent chrome.exe process (the parent process to all of the chrome.exe children processes that are automatically created per 'grouped' tab by the Chrome application) is the only thread and subsequently the process itself that remains frozen and unable to be restarted, killed, suspended, or otherwise terminated so that the application can be effectively revived and restored to its normal state of operation.
After freezing, this process cannot be killed even with such robust and advanced applications as SysInternals's Process Explorer or any other type of advanced process killer. I've tried to give administrator privileges to the advanced process termination programs to assist in overpowering this stubborn thread's tenacity, but to no avail. The ONLY thing that eventually kills the rogue process is a complete reboot of the system.
I have since upgraded to the latest version of Chrome since I first posted to this thread, but I am still running a Windows Vista x64 system. I will upgrade to Windows Seven very soon, but at the beginning of this past summer I also tested the Windows Seven RC.1 as a dual boot OS on my current hardware setup to check out the new features and everything inside of Windows Seven. I installed Chrome and all the other software that I frequently use and I also had the same issues on it leading me to believe that the problem was not resolved by a Windows Seven upgrade or anything to do specifically with Windows Vista, but possibly the new Windows platform and the x64 breed of platforms.
Current I am using:
Windows Vista x64
And I have discovered that the following process has a thread that becomes stuck in an interesting process state called "Wait:Executive" that is unable to be restored without a complete reboot of the system.
When a process or thread is in the "Wait:Executive" state, it cannot be effectively killed, terminated, restarted, suspended or otherwise brought back to life WITHOUT a complete system reboot on all Windows Vista or Windows Seven systems.
So, my current root cause analysis is that the CAUSE is directly related to Flash and or the x64 platform and a possible memory bottleneck or overload issue, but that the EFFECT is a stuck overseer process (the parent chrome.exe process) and its stuck thread that both maintain an unresolvable state. The ONLY REMEDY for this unresolvable state is a complete reboot of the system, until somebody can find an effective way to kill a process or thread in the "Wait:Executive" state without rebooting the system. If the user community can find a solution to the "Wait:Executive" state issue, then there is no need for this discussion other than notifying Google of the persistent problem related to some sort of memory overload most likely related to Flash and x64 Windows platforms.
Regarding my thoughts about the root cause being a memory overload or bottleneck issue, I must preface how I came to this hypothesis. To begin, I only have 4 GB of physical memory installed on my machine. I purchased 8 GB, but only 4 GB were detectable by my motherboard. I have yet to resolve that hardware issue. It has something to do with voltages and some sort of esoteric compatibility beyond the surface of the traditional specifications for memory module comptability with motherbaords. The reason I mention this anecdote is that my system is limited in physical memory access and I notice frequently that my virtual memory is in the 5 to 9 GB range while my physical memory hovers around 3.5 to 3.9 GB although sometimes it can reside down in the 2.5 to 3 GB range.
Anyway, I have found that Gmail and other tabs within Chrome use an enormous amount of memory. Consistently Gmail is around 100 to 200 MB, and Facebook around 100 MB, but a few Flash heavy applications have also existed at or around 100 to 300 MB. When I was playing this one Flash based game online, the Flash plugin would spike in memory to about 300 MB and the CPU for the plugin was the maximum per every Chrome tab thread-process entity. In fact, the majority of the time shortly before a major Google Chrome hiccup, the Flash plugin tab-thread-process is always using an enormous amount of memory and CPU resources. No other process has come close except for maybe Gmail, but as I found out, most webpages use some Flash within the page, so I surmise that the Flash plugin is the culprit and not any individual webpage. You can easily find out which pages use Flash and which do not by manually crashing the Flash pluing within the Google Chrome "Task Manager". Almost every single webpage contains some Flash component whether its an advertisement or actual functionality that is dominant for the webpage.
This leads me to believe that Flash is the culprit and that its massive consumption of resources, mainly memory, somehow might be interfering or interacting improperly with the x64 Windows memory mechanisms and essentially the available memory allocated for the Google Chrome process. The actual allocated memory might be severely restricted by the operating system's paging constraints that are limiting the available physical memory (quickly allocated to a running process versus virtual memory which requires disk I/O access). A lack of physical memory available to the Google Chrome application and all of its threads and processes especially when Flash suddenly begins to balloon in memory and CPU consumption could possibly trigger a system level fault that leaves the main Google Process in an unrecoverable state that Microsoft does not have a quick solution to revive it and possibly for a good reason maybe because of stability issues related to memory access. In any case, these are my observations, inferences, assumptions, and best theories for why the Chrome application keeps having hiccups on my system and why it appears that this is not an isolated incident and most likely a tricky and complex problem that is occuring on many x64 Windows systems.
I love Google Chrome so much that I deal with this annoyance, but I do hope that this issue is resolved or fixed and at the least given an option to restart Google Chrome into the normal mode of operation without restarting my entire system. Heck, if the "End Process" button within the "Task Manager" inside of Google Chrome itself was actually allowed to self-terminate the "Browser" tab-thread-process that appears within the "Task Manager", then I think I might be able to gain traction on this problem, but that appears to be a design decision by Google to restrict access to the overseer process of the application since this is a multi-process application.
To Open it click on the Page Icon (top-right) > Developer > Task Manager.
You should click on everything in chrome with the left mouse button. middle mouse wheel and right mouse button. Also go back and do them with the shift key pressed. You will be amazed at all of the hidden stuff you will find. Do this with every application on your computer and you will learn more in a day that most people do in a lifetime. :))
I cannot seem to kill the underlying frozen Google Chrome manager process that performs all of the background interprocess communication and things like the Downloads, History, and Speeddial tabs.
I also believe that Adobe Flash not being properly supported for x64 systems is the main trigger for crashing Google Chrome's manager process which leads to this condition.
The only solution that I have found is to restart my entire computer which is very lame.
Mind you, Google Chrome still works, but with reduced functionality. The Speeddial, History, and Downloads are not functioning and the cookies are cleared or inaccessible when this condition occurs. Also, the memory function of which tabs are open is lost and not accessible.
Any ideas on how to kill the rogue process so that I can restart Chrome without having to restart my entire computer? This would obviously be a temporary solution to the underlying problem causing the initial crash, but it would make my life easier and allow me to continue with Chrome as a very happy user.
As it is, I'm so happy with Chrome that even with this huge annoying problem, I still do not mind too much to restart my computer or even to just continue using Chrome in the defunct mode because it loads websites with such great speed thanks to making each tab a separate process and thereby distributing the CPU loads on my cores coupled with the amazing speed at which it loads and creates a new tab. There is no browser even close to the speed of Chrome and this is the sole reason I use it. Forget about Firerfox, IE, Opera, and Safari. None of them allow me to click 100 webpages and allow them to load in the background without any sort of a pause or delay.
What is more, Chrome seems to lock up TCP/IP stack - I can close Chrome window, but there still is a chrome.exe process in my TaskManager. I can't kill it even with TASKKILL /F /T /IM chrome*
When chrome freezes, and I close it's window, also other browser (Firefox 3.5) doesn't seem to be loading pages, which really annoys me.
Flash is the main trigger for Chrome lock-up, I believe, or maybe the 64-bit OS.
I'd be grateful if new releases of Chrome would fix that problem.
Could you let me know the answers to the questions below? It may help us get some leads as to what's going on.
- When does this problem occur? Does it only happen when you visit certain sites? If so, which sites?
- Kleskowy, you mentioned that this may be related to Flash. Which version of Flash are you using? You can find out by entering "about:plugins" into the Google Chrome address bar, and scrolling down to the section for Flash.
- Finally, do you have any security software installed? If so, which ones?
Thanks for your help.
I also think that it is related to Flash, possibly the lack of a 64-bit version of Flash. I am also using an x64 Vista. I also noticed this same problem with the Windows Seven RC1 x64 edition. I'm using version 10.0 I think. I would try to "about:plugins", but the main Chrome process has crashed already and I do not have time to restart my computer just to kill that process so that I can bring Chrome back to normal. All of those main functions of the main Chrome process are inaccessible such as the Opera-styled dial pad page, history, downloads, and about:plugins....etc....
I have McAfee VirusScan 8.7.0i, ClamWin 0.95.2 ( http://www.clamwin.com/ ), and just Windows Defender and Windows Firewall. I have Zone Alarm installed, but disabled because it requires me to purchase it now even though they advertise the free version on their website which the download does not work for some reason.
I personally believe that Flash is the culprit. I notice the memory go waaaaaay up for the Flash tab process and the CPU of the Flash tab process also spikes after an incident occurs. Under normal operation, I notice no problems until suddenly Flash gets stuck hanging on some sort of calculation maybe.
As far as I understand, the Flash plugin and so on have not been rewritten or released for the x64 architecture. Currently they are using the x32 version running under a virtual mode of some type. ( http://blogs.zdnet.com/Bott/?p=509 ) I still do not think that they have corrected the problem.
Of course I would like Chrome and Flash to behave properly, but at the least, I would like to be able to purposely crash/kill the main Chrome process after an incident so that I can restore Chrome to normal operation without having to restart my entire machine. I've tried many things from DiamondCS's Advanced Process Termination software to other esoteric ways to kill processes. I've tried killing process trees with System Internal's Process Explorer running in Administrator mode and to no avail, nothing seems to work except restarting the machine.
On my device, I have a three-part corporate-installed McAfee HIPS program that must stay installed. I found that by disabling just the McAfee firewall portion of the Host Intrusion Prevention program, this problem never occurred again!
McAfee really needs to figure out the problem with their network filter drivers...
Some community members might have badges that indicate their identity or level of participation in a community.
Member levels indicate a user's level of participation in a forum. The greater the participation, the higher the level. Everyone starts at level 1 and can rise to level 10. These activities can increase your level in a forum:
- Post an answer.
- Having your answer selected as the best answer.
- Having your post rated as helpful.
- Vote up a post.
- Correctly mark a topic or post as abuse.
Having a post marked and removed as abuse will slow a user's advance in levels.
View profile in forum?
To view this member's profile, you need to leave the current Help page.
Report abuse in forum?
This comment originated in the Google Product Forum. To report abuse, you need to leave the current Help page.
Reply in forum?
This comment originated in the Google Product Forum. To reply, you need to leave the current Help page.