sodcalculator

10 Tech How-To

Fix Client Side Exception Error in Chrome

Guide 10-48151 · Updated · Step by step

This guide walks you through fixing the “Application error: a client side exception has occurred” message in Google Chrome. This error typically appears when a web app’s JavaScript crashes, often due to corrupted browser data, outdated extensions, or a glitch in the site itself. The steps below resolve the issue in most cases, from simple refreshes to clearing site data.

What You’ll Need

  • Access to Google Chrome on your computer (Windows, Mac, or Linux)
  • The URL of the site showing the error
  • Optional: a backup of your bookmarks (for the reset step)

Step-by-Step

  1. Refresh the page. Press Ctrl+R (Windows/Linux) or Cmd+R (Mac). A temporary network hiccup or a one-time script error often clears with a reload. If the error persists, move to the next step.
  2. Hard reload the page. Press Ctrl+Shift+R (Windows/Linux) or Cmd+Shift+R (Mac). This bypasses the browser cache and reloads all scripts from the server. If the issue is a stale cached file, this fixes it.
  3. Try the site in an Incognito window. Click the three-dot menu (top-right), then select New Incognito Window (or press Ctrl+Shift+N / Cmd+Shift+N). Navigate to the same URL. If it works there, the problem is likely caused by an extension or cached data in your normal profile.
  4. Disable browser extensions. If Incognito works, go to the three-dot menu > Extensions > Manage Extensions. Toggle off all extensions, then reload the problematic page. If it loads, turn extensions back on one by one to find the culprit. Once identified, either remove it or check for an update.
  5. Clear cached images and files. Click the three-dot menu > History > History (or press Ctrl+H / Cmd+H). On the left, click Clear browsing data. In the dialog, set the time range to All time, check Cached images and files, and optionally Cookies and other site data (this will log you out of most sites). Click Clear data, then reload the page.
  6. Clear site-specific data. If you don’t want to log out of everything, go to the site showing the error. Click the lock icon (or the “Not secure” icon) in the address bar, then Site settings. Scroll down to Clear data and click it. Confirm, then reload the page.
  7. Update Chrome. Go to the three-dot menu > Help > About Google Chrome. Chrome will check for updates automatically and install them. Relaunch Chrome after updating.
  8. Reset Chrome settings. If nothing else works, go to the three-dot menu > Settings > Reset settings (or Advanced > Reset and clean up on some versions). Choose Restore settings to their original defaults. This disables extensions, clears temporary data, and resets search engines, but keeps bookmarks and passwords. Confirm and reload the site.
  9. Check if the site is down. If the error persists after all steps, the problem may be on the website’s end. Try accessing the same site on your phone or another browser. If it fails everywhere, wait a few hours and try again.

Common Mistakes

  • Skipping the hard reload. A normal refresh often doesn’t clear a corrupted cached script. Always try Ctrl+Shift+R before clearing data.
  • Clearing all browsing data too aggressively. Clearing cookies and site data logs you out of every service, which can be frustrating. Prefer the site-specific clear option first.
  • Disabling extensions one at a time too quickly. If you disable all and then re-enable several at once, you won’t know which one caused the issue. Test the page after each single re-enable.
  • Assuming it’s your fault. This error is often a bug in the web app itself. If you’ve tried the steps above and the site still fails, it’s likely not something you can fix on your end.

Tips

  • Keep Chrome updated. Browser updates often fix underlying JavaScript engine bugs that trigger this error.
  • Use a different browser temporarily. If you need to access the site urgently, Firefox or Edge may handle the broken script differently and load the page.
  • Report the issue. If the site is yours or you have a support channel, send them the exact error message and the steps you took. This helps them fix the underlying code.
  • Check for hardware acceleration issues. In rare cases, GPU rendering glitches cause this. Go to Settings > System and toggle off Use hardware acceleration when available, then relaunch Chrome.

Troubleshooting

If the error persists after following all steps, try these additional checks:

  • Disable all extensions in Incognito. Some extensions force themselves into incognito mode. Check the extension details and ensure “Allow in Incognito” is off for all.
  • Create a new Chrome profile. Go to your profile icon (top-right) > Add > Continue without an account. Test the site in the new profile. If it works, your original profile has corrupted data. You can migrate bookmarks and passwords manually.
  • Run Chrome’s cleanup tool. Go to Settings > Reset and clean up > Clean up computer and click Find. This scans for harmful software that might interfere with scripts.
  • Check your system clock. An incorrect date/time can break HTTPS certificates and cause script errors. Ensure your system time is set to automatic.
  • Try disabling your antivirus temporarily. Some security software intercepts web traffic and corrupts JavaScript. If disabling it fixes the issue, add an exception for the site.

Frequently Asked Questions

Q: Will clearing my browsing data delete my saved passwords?
A: No. Clearing cached files and cookies does not remove saved passwords. Passwords are stored separately and only deleted if you specifically choose “Passwords and other sign-in data” in the clear browsing data dialog.

Q: This error only happens on one website. Why?
A: It usually means the website’s code has a bug or uses a feature that conflicts with your browser version. The site’s developers need to fix it. You can try updating Chrome, but the fault is often on their end.

Q: Does this error mean my computer has a virus?
A: Not usually. It’s a JavaScript runtime error within the browser. However, if you suspect malware, run Chrome’s cleanup tool and a reputable antivirus scan.

Q: I’m a developer. How do I debug this?
A: Open Chrome DevTools (F12), go to the Console tab, and reload the page. The red error messages will show the exact file and line number where the exception occurred. This is the fastest way to pinpoint the bug.

Q: Will resetting Chrome delete my bookmarks?
A: No. The “Restore settings to their original defaults” option keeps your bookmarks, history, and saved passwords. It only resets settings like your homepage, search engine, and disables extensions.

Q: The error appears on a banking or government site. What should I do?
A: Do not attempt workarounds that disable security features. Try a hard refresh first. If that fails, contact the site’s official support. Never disable antivirus or security extensions on sensitive sites without guidance from their support team.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →