Google Chrome is one of the most popular internet browsers on the planet. However, it is not without its flaws. A lot of users have been complaining that Chrome keeps crashing on Mac. If you’re a Chrome user and facing issues running the browser on your Mac, then we’ve got some possible solutions for you.
Those who rely on Google’s services and the ecosystem, will obviously want to use Chrome on their Mac. Everything becomes easier after installing Chrome and switching it for Safari. Chrome crashing on Mac is not uncommon, and can be fixed easily. We’ve got a detailed troubleshooting guide for you, which offers possible fixes for Chrome crashing on your Mac. Let’s take a look at some of these fixes.
Google Chrome Keeps Crashing on Mac? How to Fix the Issue
Amiga Forever for macOS: We'll soon start working on a Mac version of Amiga Forever, inclusive of the high-quality playback and authoring functionality our customers are enjoying on Windows. If you would like to be informed about updates concerning Amiga Forever for macOS, please ent. I supposed it 'Mac OS 9 usage dwarfs OS X in creative fields September 22, 2003 - 16:04 EDT. Following. Apple will host its annual Worldwide Developers Conference (WWDC) on schedule this year, with the event kicking off on June 7 and concluding on June 11. Like last year, it will be an online-only.
There could be several reasons as to why Chrome keeps freezing on your Mac computer. Although this isn’t a very common issue, some users do face it once in a while. For some, the browser crashes as soon as they click on the icon, while some complain about tabs not working or pages not loading.
- Apple has been on the yearly upgrade cycle for macOS for a few years now, so it feels like by the time we get the X.4 revision of a new version of macOS, we are getting ready to kick off a summer.
- The history of macOS, Apple's current Mac operating system originally named Mac OS X until 2012 and then OS X until 2016, began with the company's project to replace its 'classic' Mac OS.That system, up to and including its final release Mac OS 9, was a direct descendant of the operating system Apple had used in its Macintosh computers since their introduction in 1984.
Google Chrome eats RAM like there’s no tomorrow, so if your Mac computer is low on RAM, then that could be the issue why Chrome keeps crashing. If your Mac is good enough and still unable to run Chrome properly, then the problem is with the browser. I’ve listed some of the most common solutions below.
Quick Access:
#1. Clear Chrome Browsing Data on Mac
If your Chrome browser isn’t loading tabs or pages properly, then you should try to clear the browsing data. To do this, you will need to do the following:
Step #1. Open Chrome on your Mac and click on the three-dotted button on the top right corner of the Chrome browser. It’s located next to your profile picture.
Step #2. Select Settings and scroll down till you find the Advanced section.
Step #3. Find the Clear Browsing Data option and click on it.
Step #4. Select All time and clear all data. This will erase everything and is similar to a factory reset.
Step #5. Check if the browser works fine now.
#2. Check for Network Issues in macOS
It is possible that the Chrome browser keeps crashing due to network issues. If the network connection isn’t working properly, then you may experience issues with Chrome. Check if your Wi-Fi connection is working, and if it isn’t, then restart the router or try to connect to another network. Now check if the browser is loading properly.
#3. Quit Chrome and Restart Mac
If the Chrome browser is stuck, then you can try to Force Quit it and do a restart. To force quit Chrome, click on the Apple() logo in the Menu bar while you’re in the browser. Here, click on the option that says Force Quit.
If the mouse/trackpad isn’t responding, then you can press and hold down ‘Command+Option+Escape‘ keys on the keyboard. Select Google Chrome and force close the browser.
You might also want to restart your Mac just to make sure everything is running normally again. Try if Chrome is working properly now.
#4. Check Extensions on Chrome
At times, the issue could be related to a bad extension that you’ve installed on your Chrome browser. This may cause the browser to keep crashing. In this case, you will have to head over to the Extension manager and delete the faulty extension. To check the problem causing extension, open Chrome in Incognito mode and then enable each extension to check which one causes a crash. Incognito mode automatically disables all extensions, and is therefore the best way to find the culprit.
To open a new page in Incognito Mode, click on the three-dotted button and select ‘New Incognito Window‘.
Now head to More Tools → Extensions to remove the faulty extension.
#5. Check for Chrome Updates on Mac
You may also want to check if you’re running the latest version of the Chrome browser. Google usually pushes updates with bug fixes, hence, it is a good idea to check for updates. To see if you’re running the latest version of Chrome, click on the three-dotted button and then select Help → About Google Chrome. If any updates are available, you will see it on this page.
You should also try to uninstall Chrome and reinstall it to see if that fixes the problem. Sometimes, it could just be that the browser didn’t install properly the first time.
#6. Turn Off Hardware Acceleration in Google Chrome
Some users suggest turning off hardware acceleration if your Chrome browser is freezing or crashing all the time. This option is available in Settings, and can be disabled easily. To turn off the feature, navigate to Settings → Advanced → and disable ‘Use hardware acceleration when available‘.
Summing Up!
Those were some of the possible solutions that you can use to fix Google Chrome crashing issues on your Mac. Most of the time, it’s something simple that’s causing the browser to not function properly. Try out all the fixes above to see what works best for you.
Read More!
Were you able to solve Chrome issues using the above mentioned fixes?
This page has two sections. First up is a table of commands, and then later in the page, you’ll find a quick and dirty guide (originally posted as its own article) on actually getting into and using the cross environment.| Command | Purpose |
| exit | Exit the crosh Shell |
| help | Display the crosh help |
| help_advanced | Show advanced crosh commands; primarily used for debugging. |
| ping | [-c count] [-i interval] [-n] [-s packetsize] [-W waittime] < destination >Send ICMP ECHO_REQUEST packets to a network host. If < destination > is “gw” then the next hop gateway for the default route is used.It works just like the ping command on other operating systems. Press Ctrl+C to stop the ping process or halt any other command in Crosh. |
| ssh | Starts the ssh subsystem if invoked without any arguments.“ssh < user > < host >”, “ssh < user > < host > < port >”, “ssh < user >@< host >”. or “ssh < user >@< host > < port >” connect without entering the subsystem. |
| ssh_forget_host | Remove a host from the list of known ssh hosts. This command displays a menu of known hosts and prompts for the host to forget. |
| top | Sets the chapsd log level. No arguments can start verbose logging. |
| battery_test [< test length >] | Tests battery discharge rate for given number of seconds. No argument will default to 300s test. |
| bt_console <agent> | Enable the Bluetooth debugging console |
| chaps_debug [start stop < log_level >] | Sets the chapsd logging level. No arguments will start verbose logging. |
| connectivity | Shows connectivity status. |
| experimental_storage < status enable disable > | Enable or disable experimental storage features. |
| ff_debug [< tag_expr >] [–help] [–list_valid_tags] [–reset] | Add and remove ff debugging tags. |
| memory_test | Performs extensive memory testing on the available free memory. |
| modem < command > [args…] | Interact with the 3G modem. Run “modem help” for detailed help. |
| modem_set_carrier carrier-name | Configures the modem for the specified carrier. |
| network_diag [–date] [–link] [–show-macs] [–wifi] [–help] [–wifi-mon] < host > | A function that performs a suite of network diagnostics. Saves a copy of the output to your download directory. |
| network_logging < wifi cellular ethernet > | A function that enables a predefined set of tags useful for debugging the specified device. |
| p2p_update [enable disable] | Enables or disables the peer-to-peer (P2P) sharing of updates over the local network. This will both, attempt to get updates from other peers in the network and share the downloaded updates with them. Run this command without arguments to see the current state. |
| rlz < status enable disable > | Enable or disable RLZ. |
| rollback | Attempt to rollback to the previous update cached on your system. Only available on non-stable channels and non-enterprise enrolled devices. Please note that this will powerwash your device. |
| route [-n] [-6] | Display the routing tables. |
| set_apn [-n < network-id >] [-u < username >] [-p < password >] < apn > | Set the APN to use when connecting to the network specified by < network-id >. If < network-id > is not specified, use the network-id of the currently registered network. |
| set_apn – c | Clear the APN to be used, so that the default APN will be used instead. |
| set_arpgw < true false > | Turn on extra network state checking to make sure the default gateway is reachable. |
| set_cellular_ppp [-u < username >] [-p < password >] | Set the PPP username and/or password for an existing cellular connection. If neither -u nor -p is provided, show the existing PPP username for the cellular connection. |
| set_cellular_ppp -c | Clear any existing PPP username and PPP password for an existing cellular connection. |
| sound < command > < argument > | Low level sound configuration. Can be used to play/record audio samples and enable beam forming on Pixel.“sound beamforming < on off >” will enable/disable the feature.“sound record [duration]” will start recording.“sound play < filename >” will play the recorded audio samples. |
| storage_status | Reads storage device SMART health status, vendor attributes and error log. |
| storage_test_1 | Performs a short offline SMART test. |
| storage_test_2 | Performs an extensive readability test. |
| syslog < message > | Logs a message to syslog. |
| tpcontrol {status taptoclick [on off] sensitivity [1-5] set < property > <value>}tpcontrol {syntp [on off]} | Manually adjust advanced touchpad settings. |
| tracepath [-n] < destination >[/port] | Trace the path/route to a network host. |
| update_over_cellular [enable disable] | Enables or disables the auto updates over cellular networks. Run without arguments to see the current state. |
| upload crashes | Uploads available crash reports to the crash server. |
| wpa_debug [< debug_level >] [–help] [–list_valid_level] [–reset] | Set wpa_supplicant debugging level. |
| xset m [acc_mult[/acc_div] [thr]]xset m default | Tweak the mouse acceleration rate. |
| xset r rate [delay [rate]] | Tweak autorepeat rates. The delay is the number of milliseconds before autorepeat starts. The rate is the number of repeats per second. |
| xset r [keycode] < on off > | Turn autorepeat on/off. If keycode is specified, it affects only that key. If not specified, it affects global behavior. |
- Find commands:
help - Find debugging commands:
help_advanced - To switch to a more bash-like command prompt:
shell - To see the version of Chrome OS running on your Chromebook:
sudo /opt/google/chrome/chrome –version- To show the operating system name:
uname -a - If the operating system is a bit old, update it using the update_engine_client command:
update_engine_client -update - To see the bios of your Chromebook, open up a command prompt (Control-Alt-T) and use the following command:
sudo /usr/sbin/chromeos-firmwareupdate -V - To record some sound from the microphone, use the sound command:
sound record NUMBEROFSECONDSLook for (or grep for) BIOS version in the output. - To see the Vital Product Data, or configuration information such as time zone, UUID, IMEI, model, region, language, keyboard layout and serial number:
sudo dump_vpd_log --full --stdout - Or to be specific about what you’re looking for, grep for it:
sudo dump_vpd_log --full --stdout grep 'serial_number' - To capture some logs for debugging, use systrace:
sudo systrace - To manage the mouse and keyboard acceleration and autorepeat options, use the xset command:
xset m - Trace a network path (like traceroute or tracert):
tracepath www.google.com - To run standard network diagnostics:
network_diag - To capture some packets while troubleshooting network connections, use the packet_capture command:
packet_capture - Check the type, version, etc on your touchpad:
tpcontrol status - You can also debug network connections by logging data going through either the wifi, cellular or ethernet interface using the network_logging command. To do so for a normal 802.11 connection:
network_logging wifi - To configure WAP information:
wpa_cli - Accept an SSL Cert by using the enterprise_ca_approve command:
enterprise_ca_approve --allow-self-signed https://entca.krypted.com
sudo ifconfig eth0- To see all of the running processes:
top - To see a user’s hid and gid, use id:
id - To see more information To ping Google:
ping www.google.com
- To see a list of the commands you’ve run:
shell_history - To close the command prompt:
exit
K Cking Mac Os 11
- To make the file system writeable, first fire up a command prompt via crosh, by using Control-Alt-T and then running the shell command at the shell prompt:
shell - Then run the following shell script to remote rootfs verification and make the file system writeable:
sudo /usr/share/vboot/bin/make_dev_ssd.sh --remove_rootfs_verification - Then reboot and do whatever it is you need to do.For example, install a vine server and run automation scripts to do regression testing. Enjoy.