A few hours ago Chrome closed on my MacBook Air with OS X Yosemite 10.10.2 and there's no way to recover it. Everytime I try to launch it quits with the message "Google Chrome has quit unexpectedly", giving me the option to send a report to Apple, Ignore, or restart Chrome. And the same happens afterwards.
This could be an issue with your user profile in Chrome. I know I've had this problem before on a Windows PC. This would make sense since uninstalling and reinstalling the application in Mac would not remove these user files.
I suppose that if the fix works, you could 'cherry pick' files and folders from the backup directory until it starts having the problem again to narrow down the file that might be the root cause of the crashing.
But this is a weird bug because it's clearly not affecting everyone, even people with the most updated version of Mac OS X (10.10.2). But according to this, the problem stems from Apple depreciating the isResting selector and then completely removing it in the most recent update.
I imagine a patch will be pushed out to canary builds over the next couple of days or Apple will send out a new driver update (but probably not since they were working to remove isResting). I would stay on the lookout for that.
OPTION 1:You could use a external mouse en disable the use of the trackpad while a USB mouse is connected. (Accessibility>Mouse & Trackpad>Ignore built-in trackpad when mouse or wireless trackpad is present)
OPTION 2:(found on Reddit) This fix is not the best solution, but it works. When you follow the instructions you'll have to run the last terminal command every time you want to run Chrome. But you can also make a chrome launcher with the automator app and the terminal command.
The problem is fixed as of December 20th, 2014 on OS X Yosemite. I'm not sure when Apple released the newer version of OS X, but currently I can open Google Chrome using the normal method and move my mouse without it crashing.
Own a 2016 MacBook Pro and running iOS Monterey 12.7. One day last week, Google Chrome stopped working. It would open (when selected) in a flash and then quit automatically without me touching anything. I've had Chrome on my computer since day 1 of owning this comp and have never had this problem.
I have tried uninstalling and reinstalling with reboots in between from the Chrome page through Safari browser and have not been successful. It downloads fine, I launch the install and move it to the APP folder just fine. Then, it doesn't work.
Thanks for posting in Apple Support Communities! Since the app is quitting on its own, we suggest following the guidance here as it can resolve this issue: If an app freezes or quits unexpectedly on Mac. You can also clear out the cache for the app by holding down the Shift key as you click to open the app.
Some Users have, and others may have not. Some Users have done a few of the steps, but for others, those steps other may not have occurred to them. Some get all their advice from Reddit, Others use ONLY StackOverflow and Apple Developer.
The audience here is VERY Broad, and as Responders, we have to tailor the advice supplied to the lowest common denominator. There will always be far more readers than responders, and these writings are available for a very long time, and users may find them by searching.
Safe mode often corrects weird software behavior by forcing the OS to do cache clearing and other housekeeping. When you're in safe boot, the machine will not be at its best performance, especially with graphics, but that's expected.
Often not required, but consider allowing the Mac to "soak" in Safe mode for an hour to allow maintenance routines and processes time to complete, then exit safe mode by restarting your Mac normally and re-evaluate the issue again.
I finally realized that the problem was, I had never completed the download. When I downloaded Chrome, it put it on my taskbar, but also put a little folder off to the side. I finally realized that I needed to click inside that folder to complete the download. Since doing that, I have not had any problems. I hope somebody finds this helpful.
Oddly enough, one random day after I had spoken to support and reinstalled my operating system (maybe 3 days later)... I went to re-download the Chrome app and it actually worked by itself. I quickly saved all my bookmarks in fear it would stop working but so far so good!
However, in those cases on a Mac, you get a message that the software you are trying to run can not be run on this computer. Occasionally it will explain what is deficient: MacOS, computer Hardware, etc.
CRASHING is Not normal behavior for ANY Mac App. It generally indicates unresolved hardware issues or Software conflicts. But more pointedly, It TYPICALLY indicates third-party speeder-uppers, Cleaners, Optimizers, or Virus scanners. or a VPN that you installed yourself.
I have a Windows Surface Pro running Windows 10. I downloaded 1Password for Windows as of today (Version 7) and every time I try to start 1Password it says 1Password quite unexpectedly. I've completely removed 1Password from my system (including the Chrome extension) and started from scratch several times. That does not resolve this.
@todd.d: To clarify, does 1Password crash as soon as you launch it or does it crash when you unlock it? I see you've got a lock screen in the background, which makes me think it's the latter, but better to be sure. Thanks! :chuffed:
In that case, @todd.d, I believe I know just what will fix you up. In most cases of this I've seen, folks have signed out of their last account recently, but I can think up a few other reasons the same issue might pop up. If you recall what you did immediately before this started happening, I'd appreciate hearing about it so we can make sure we test all possible paths here when we get a fix ready, but regardless here's how to fix it:
Hi @bundtkate, I tried your directions verbatim and my issue still existed. I made sure the data folder was renamed just as the link you provided indicated. However, I completely deleted the 1password folder in the appdata/local, uninstalled 1Password completely, then reinstalled from scratch and now it's working.
I think what instigated this mess was that I borrowed my son's Surface pro for a few days. I used the app and chose the option to sign him out. I then signed in with my master account. All was well until I was ready to give the laptop back to him. I think the sequence as that I then signed out of my account and attempted to sign him in. Then it started having issues. Hope this helps. Thanks.
Todd
Thank you for keeping us posted! I am glad to hear that starting from scratch helped. There might be several different reasons for crashes in 1Password, so we need to investigate. We will try to reproduce this crash using the info you shared and fix this behaviour, if it is incorrect.
Recently my google chrome quit unexpectedly and now it will not launch and it keeps giving me the reopen option but continues to shutdown. its only doing this with my own username and not any others from the laptop.
Thanks for reaching out in Apple Support Communities! If we understand correctly, the Google Chrome app is quitting unexpectedly on your Mac, and when attempting to reopen the app it continues to shutdown.
Open the System Preferences, and click on the International pane. On the Language tab, rearrange the bottom two languages on the list, then close System Preferences. This recreates a language preference which can keep Acrobat from launching.
In the Utilities folder inside your Applications folder, you'll find an app called "Console". Run that. When it's running, choose Preferences from the Console menu. In the Preferences dialog choose the 'Crashes' tab. Check the 'Enable crash reporting' checkbox.Now, make Acrobat Reader crash (unexpectedly quit) at launch. You should then find a file called 'Acrobat Reader.log' (or something similar) in the Logs folder in the Library folder in your Home directory.Paste the contents of that log file into the forum. It might not help one bit, but it's worth a try.-Vince
Vince told me that it looked like a font problem, so I contacted Extensis (I use suitcase to manage my fonts). They suggested deleting my suitcase prefs (in user, library, prefs - com.extensis... and the whole suitcase folder). He also suggested purchasing Font Doctor since I have so many old fonts. I deleted the prefs and ran Font Doctor. Then I kept getting an error that the fonts were missing when I tried to create a pdf. I compared my Base 14 fonts in Distiller to what was in my system 9 font folder and found they weren't all in the folder. I put them back in the folder, restarted and viola - it works! Hope this helps someone!
I've uninstalled all my Adobe products trying to work this out, reinstalled, and only had the problem with Acrobat 5 afterwards. It was driving me bonkers!I didn't even install foreign (to me) languages the last time I installed OS X. swapped the bottom two on the System Preferences list, and I'm back to Acrobat ok. Thanks to all...les owens
gastonia, nc
iMac G4 800mhz 512mb ram HP 960. Acrobat 5, Acrobat Reader 5.0.5, Go Live 6.0, Photoshop Elements 2.
Whenever i click File>Preferences, my adobe will quit unexpectedly. I have tried uninstalling, re-download, everything I could. And also I cannot see the tool bar on my right handside. I will attach a photo here. Please help me guys!!!
He was using Adobe Reader 11.x, but this week had problems printing. His old Adobe Reader crashed when printing, when opening preferences, and when trying to markup reader-enabled files. Removed the old Reader, then installed Reader DC latest version. Had same problems. Can print PDFs opening them in Chrome browser, so there's a partial work-around to get him by right now. But Adobe Reader DC, to be kind, is rather unresponsive.
d3342ee215