Do you see "Whoa? Google Chrome has crashed" Try about: conflicts.

[rUChIRr]

If you are seeing "Whoa! Google Chrome has crashed" a lot, you may have malicious software or third party that conflicts with Google Chrome. To see if you have any known conflicts, you can write about: conflict in the address bar. Most of you will see No conflicts detected and then a long list of modules that are loaded into the process for the Google Chrome browser. Some of you may see conflict suspicion or conflict known, in which case there will be a link for more information on the solution of the problem. In general, keep computers safe and clean just by downloading software from reputable suppliers and often to scan your computer for malware.

[GhostRider]

It would be really great to get information like this for Mac Chrome crashes at least every time you open it. I cleared cookies, temp files, disabled all extensions, uninstalled and reinstalled and nothing has helped. This has been going on for a month and a half now and there is never any information about what we can deal with Macs to get Chrome working properly and it seems that any issue I read about people who have these troubles on a Mac are not answered by employees Google. It's pretty annoying.

[arturro]

I just got so sick of all crashes in Chrome, I uninstalled everything related to Adobe Flash Player and all is well now. I am not technical intelligent, but I think Google Chrome already has integrated Flash Player and updates as needed, so I'm keeping under cover in a while. I've also found the solution to all my Chrome Flash / Shockwave accidents. Uninstall Mozilla Firefox on computer. Firefox plug-in appears to conflict with Chrome plug-in. After removing any additional version of Flash Chrome still crashing. After a reboot, the crashing will stop.

[Grohu]

First, when Chrome crashes on boot, try adding the command - line diagnostic indicators. Here are the steps to add command line flags: First locate the chrome or chrome shortcut. There must be on the desktop and start menu - either one will work! Second, click on the shortcut with the right mouse button and select Properties. Third, find the target box (which will be highlighted when the properties screen appears.) Then left click at the end of the line (after chrome.exe) and press the spacebar. Add your modifier command line. The result looks like this: C: \ Users \ LEEM \ AppData \ Local \ Google \ Chrome \ WINDOWS \ chrome.exe - Bookmark menu. Now, finally, to add more than one, separate each switch with a space. The result looks like this:
C: \ Users \ LEEM \ AppData \ Local \ Google \ Chrome \ WINDOWS \ chrome.exe - bookmark-menu - enable-ghost-tabs. Second, on: the conflict is currently available only in English but other languages will be available in the future.

[Zacharia]

I think I found the cause of accidents Flash in Chrome. By using Chrome, which installs and updates the plug-in and flash automatically? But when you also use browsers other than as IE and FF, you must install Flash yourself. I found that these facilities are conflicting and different cause Chrome to sleep in flash sites such as Facebook applications. Some days ago I uninstalled all the flash players, both Macromedia and Adobe, and a fresh start Chrome, this software has been reinstalled for Chrome itself. In fact, the browser takes a little time to implement in this case, but you can follow the progress at about chromium. Since then, everything runs smoothly and without accidents. But when using browsers other than make sure you do not install Flash again by itself, because the clash will start again.

[Sadiee]

Try this automatic updating of Flash which is the problem. Then delete the NPSWF32.dll C: \ Documents and Settings \ \ Local Settings \ Application Data \ Google \ Chrome \ WINDOWS \ Plug-in and began to Chrome. It worked. After that, reinstall flash on the website of Adobe. Everything is working perfect now. These have to be open to Chrome, but immediately stopped for the first time since the night before. So it looks like a problem with Flash was indeed the culprit of my WinXP SP3 32-bit running 10.0.648.114 Chrome beta.

[fellah]

I found the solution! It happened with me many times, and I was never able to find an answer to this, so please keep in mind to keep giving me acknowledgment, open the task manager and click processes. That there are processes using Google called accident or something and a very alike name right above or below it. You end both processes. It should work fine. I really this help you to solve the problem.