If you always use the Google Chrome browser in browsing the internet, then you might have come across an error message saying, “He’s dead, Jim!” along with a funny looking face that’s peeking its tongue out and another detailed message saying, “Either Chrome Ran out of memory or process for the webpage has terminated for some other reason. To continue, reload the webpage or go to another page”.
This error message in Google Chrome is actually quite famous and it appears for various reasons but it may have something to do with a memory issue. The Google Chrome browser is known to consume a lot of memory and the more web pages you open and load, it takes up more resources. Thus, the first thing you need to do when you encounter this error is to simply click the Reload button to continue browsing the internet or close the browser and then open it again. On the other hand, if you keep seeing this error message, then that’s a whole different story as you have to take some action to prevent it from popping up again, for good. Follow the instructions given below to fix the error in Chrome.
Option 1 – Reduce Google Chrome’s memory usage
The first thing you can try is reducing the memory usage of the Chrome browser. However, this option has a bit of a disadvantage. If a website crashes, all the instances of that website will also crash although other open tabs and websites won’t be affected. This process is referred to as “Process-per-site” mode which you will have to launch Chrome within this parameter.
Option 2 – Run Google Chrome with Strict Site Isolation
Aside from reducing Chrome’s memory usage, you can also run the browser with the Strict Site Isolation which makes sure that the crashing of one tab in the browser won’t affect the entire Windows as this feature will run every website you open on its own isolated process.
Option 3 – Run the built-in Malware Scanner and Cleanup tool in Chrome
In case you don’t know, there is actually a built-in malware scanner and cleanup tool in Chrome that helps you get rid of any unwanted ads, pop-ups, and even malware, as well as unusual startup pages, toolbars, and other things that could affect the performance of the browser.
Option 4 – Reset Google Chrome
Resetting Chrome can also help you get rid of the “He’s dead, Jim!” error message for good. Resetting Chrome means restoring its default settings, disabling all the extensions, add-ons, and themes. Aside from that, the content settings will be reset as well and the cookies, cache, and site data will also be deleted. To reset Chrome, here’s what you have to do:
- Open Google Chrome, then tap the Alt + F keys.
- After that, click on Settings.
- Next, scroll down until you see the Advanced option, once you see it, click on it.
- After clicking the Advanced option, go to the “Restore and clean up the option and click on the “Restore settings to their original defaults” option to reset Google Chrome.
- Now restart Google Chrome.
Option 5 – Perform a clean reinstall on the Chrome browser
Although reinstalling any program is easy, not so much for Google Chrome as you need to make sure that the User Data folder is deleted before you reinstall it.
- Tap the Win + R keys to open the Run prompt.
- Then type %LOCALAPPDATA%GoogleChromeUser Data in the field and hit Enter.
- Next, rename the “Default” folder inside the path you were redirected to. For instance, you can rename it to “Default-old”.
- After that, install the Chrome browser again.
Option 6 – Try to flush the DNS and reset the TCP/IP
There are instances when a network goes into haywire because of a bad DNS. Thus, a bad DNS might be the one that’s causing this headache so it’s time for you to reset the entire network to resolve the issue. To reset the network, here’s what you have to do:
- Click the Start button and type in “command prompt” in the field.
- From the search results that appear, right-click on Command Prompt and select the “Run as administrator” option.
- After opening Command Prompt, you have to type each one of the commands listed below. Just make sure that after you type each command, you hit Enter
- ipconfig /release
- ipconfig /all
- ipconfig /flushdns
- ipconfig /renew
- netsh int ip set dns
- netsh winsock reset
After you key in the commands listed above, the DNS cache will be flushed and the Winsock, as well as the TCP/IP, will reset.
- Now restart your computer and open Google Chrome then try opening the website you were trying to open earlier.
Note: You can also try changing the DNS server to the Google Server, i.e. 8.8.8.8, and then see if it works for you or not.
Option 7 – Disable both the antivirus and firewall temporarily
As you know, both the firewall and antivirus programs are there to protect the operating system from any malicious threats. So if they find that there is some malicious content in a website you are visiting, they will block the site right away. Thus, it could also be the reason why you’re getting the “He’s dead, Jim!” error so you need to disable both the firewall and antivirus program temporarily and then try opening the website again. If you are able to open the website, you need to add this site as an exception and then enable the firewall and antivirus program back.
History of Commodore
With sales booming and the early reliability issues with the hardware addressed, software for the C64 began to grow in size and ambition during 1984. This growth shifted to the primary focus of most US game developers. The two holdouts were Sierra, who largely skipped over the C64 in favor of Apple and PC compatible machines, and Broderbund, who was heavily invested in educational software and developed primarily around the Apple II. In the North American market, the disk format had become nearly universal while cassette and cartridge-based software all but disappeared. So most US-developed games by this point grew large enough to require multi-loading.
At a mid-1984 conference of game developers and experts at Origins Game Fair, Dan Bunten, Sid Meier, and a representative of Avalon Hill said that they were developing games for the C64 first as the most promising market. By 1985, games were an estimated 60 to 70% of Commodore 64 software. Over 35% of SSI's 1986 sales were for the C64, ten points higher than for the Apple II.
Everything was great for Commodore but the industry was moving forward and by the year 1988, PC compatible computers were stated to be the largest and fastest-growing home entertainment systems pushing C64 on to second place. Also, Nintendo’s gaming system has started to take hold in the world with amazing 7 million systems sold in 1988 only.
By the year 1991, many developers exited the gaming market for Commodore 64 home computer system and its popularity started to fall due to lack of software and not so many hardware changes.
Commodore announced that the C64 would be finally discontinued in 1995.
However, only one month later in April 1994, the company filed for bankruptcy. When Commodore went bankrupt, all production on their inventory, including the C64, was discontinued, thus ending the C64's 11 and a half year production.
Zak McKracken and the Alien Mindbenders
If you are not keen on spending money for reliving and checking games or software of C64 here are some links to help you to at least experience part of it completely free.
Commodore 64 Emulator
C64 Game ROMs
The true cause is that there is no working Border Gateway Protocol (BGP) routes into Facebook's sites. BGP is the standardized exterior gateway protocol used to exchange routing and reachability information between the internet top-level autonomous systems (AS). Most people, indeed most network administrators, never need to deal with BGP.
Cloudflare VP Dane Knecht was the first to report the underlying BGP problem. This meant, as Kevin Beaumont, former Microsoft's Head of Security Operations Centre, tweeted,
"By not having BGP announcements for your DNS name servers, DNS falls apart = nobody can find you on the internet. Same with WhatsApp btw. Facebook has basically de-platformed themselves from their own platform."
Many people are very annoyed by this and with the fact that they cannot use their social media platforms but it seems that Facebook employees are in even bigger annoyance as it was reported that Facebook employees can't enter their buildings because their "smart" badges and doors were also disabled by this network failure. If true, Facebook's people literally can't enter the building to fix things.
Reddit user u/ramenporn, who claimed to be a Facebook employee working on bringing the social network back from the dead, reported, before he deleted his account and his messages:
"DNS for FB services has been affected and this is likely a symptom of the actual issue, and that's that BGP peering with Facebook peering routers has gone down, very likely due to a configuration change that went into effect shortly before the outages happened (started roughly 1540 UTC). There are people now trying to gain access to the peering routers to implement fixes, but the people with physical access is separate from the people with knowledge of how to actually authenticate to the systems and people who know what to actually do, so there is now a logistical challenge with getting all that knowledge unified. Part of this is also due to lower staffing in data centers due to pandemic measures."
Ramenporn also stated that it wasn't an attack, but a mistaken configuration change made via a web interface.
Both BGP and DNS are down, the "connection to the outside world is down, remote access to those tools don't exist anymore, so the emergency procedure is to gain physical access to the peering routers and do all the configuration locally."
Technicians on site don't know how to do that and senior network administrators aren't on site.
It seems that it will all be down for a couple of more hours before the issue is resolved. 