RESULT_CODE_HUNG typically refers to a situation where the renderer process becomes unresponsive or “hung” in the Chrome app. It can happen due to corrupt JavaScript code, excessive resource consumption, or other issues within the webpage or browser.
In order to fix this, you can hard refresh the web page, check in incognito mode, and switch to different networks. delete cache and data, disable heavy extensions, and switch to different DNS settings.
In this guide, we have shared the troubleshooting methods to fix the code hung error in the Chrome browser.
On this page, you can find and jump to:
Method 1: Basic Browser Troubleshooting
Before moving on to the slightly advanced fixes, let’s start with some basic troubleshooting techniques, which are often considered the best Kickstarter.
- First off, hard reload the page using the + keyboard shortcut, OR you could hold the or key and click on the Reload
icon situated left of the address bar.
- If that doesn’t work out, try accessing that website in incognito mode. To do so, use the + + shortcut key combinations to open a new Incognito window. Then type in the URL in the address bar and see if the page can load correctly.
- Likewise, you could also switch the connection mode from wireless (WiFi) to wired (ethernet cable). Or try switching to a different network by sharing your device’s carrier data via the Hotspot.
Verify if any of these three methods rectified the error. If your answer is in a negative tone, then here are a few other methods that you should try.
Method 2: Delete Browser Cache and Website Data
If a lot of temporary data accrues over time, it could conflict with the proper functioning of the browser. As a result, you should frequently delete these data after regular intervals.
If you haven’t done so in quite a while, it seems to be a perfect time, as it might also fix the underlying issue.
- Launch the Chrome browser and type in the below URL in its address bar:
chrome://settings/clearBrowserData
- Now enable the tick-mark for Cookies other site data, and Cached images and files.
- Hit the button and wait for the process to complete.
Once done, relaunch Chrome and see if the browser error has been fixed.
Method 3: Disable Browser Extensions
In some instances, a third-party extension could cause a few issues with the loading of the websites. However, identifying the culprit could be effort-taking, especially if several extensions are installed.
The only way out is to disable all the extensions and re-enable them one at a time until you can recreate the issue. Once you have identified the extension that resulted in this error, you should consider removing it from your PC.
- Open Chrome on your PC and copy-paste the below location into the Omnibox:
chrome://extensions
- This should take you to the list of installed extensions.
- Disable all the extensions by turning off their toggle button.
- Now try reloading the concerned page, and if the issue has been rectified, re-enable all the extensions one at a time.
As and when you can recreate the issue, remove the last enabled extension. However, if the extensions weren’t the root cause error, then turn your attention to other fixes shared below.
Method 4: Switch to Google DNS
If there are any issues with your Internet Service Provider’s DNS server, you could try switching to an alternate one. By default, the DHCP (Dynamic Host Configuration Protocol) instructs the browser to pick up your ISP’s DNS address. However, you could manually instruct the DHCP to pick up one of the public DNS servers, such as Cloudflare or Google.
In this regard, Chrome has in-built profiles for these public DNS servers. You only need to select the desired profile and complete the task.
- Launch Google Chrome and head to its Settings page under the More
menu. - Switch to the Privacy and Security section, and click the Security tab.
- Enable the Use Secure DNS toggle (if that isn’t enabled by default).
- Next up, switch to the With Custom radio button.
- Select Google (Public DNS) from the drop-down.
Doing so will set 8.8.8.8 as the primary DNS and 8.8.4.4 as the secondary one. Now try opening the site that was earlier displaying the error; it should now be accessible.
Bottom Line
In my case, the ad blocker extension repeatedly caused the browser issue. After I removed the extensions, I no longer encountered the error message on any sites.
Lastly, if you've any thoughts or feedback, then feel free to drop in below comment box. You can also report the outdated information.
