Google Chrome Dev-tools crashes. Error code: STATUS_BREAKPOINT - javascript

I have been working on a chrome extension to interact with some DOM elements and put it in a JSON format and have found a bug in my code.
I am able to place the breakpoint in the window but once I reload the page so my script gets reinserted to run from the start my window crashes with the following error message
I have tried to do the same thing on other websites and have had no issues using breakpoints on them. Only this one website seems to have an issue with it.
I have gone through chrome's suggested trouble shooting by reinstalling chrome and clearing my cache and browser history but that also did not work.
Has anyone else encountered and solved this error in the past?

Related

While running VS Code Live Server (Go Live), the browser is crashing. I am using Google Chrome as default

While running VS Code Live Server (Go Live), the browser is crashing with the below mentioned error. I am using Google Chrome as default. I re-installed VS Code after uninstalling completely (from cache even), restarted browser, and then restarted PC as well with no use. When I checked "Use Local Ip" in LiveServer>Settings:, server is taking too long to respond and eventually fails to load the page (Error: "This site can't be reached"). Another important thing is that Chrome is opening every other website properly. This problem exists only when opening VS Code Live Server. Below is the error code:
Chrome Browser Error:
"Aw, Snap!
Something went wrong while displaying this webpage.
Error code: STATUS_BREAKPOINT"
Another popup is also showing up simultaneously:
"DevTools was disconnected from the page.
Once page is reloaded, DevTools will automatically reconnect."
(This didn't seem like a bug in the code of script.js)
Found the Solution:
Indeed it is a bug in the code of script.js.
If you are having exactly the same problem as I described, let us first see what we don't need to do, as I found these suggestions everywhere, and none will work when both VS Code and your browser are perfectly fine (they only appear to be not working):
No need to restart or reinstall VS Code.
No need to restart or reinstall browser.
No need to restart the PC
No need to disable browser extensions or VS Code extensions.
No need to change LiveServer Custom Browser; you can keep it
default.
No need to change LiveServer>Settings>Use local ip or Use browser
preview (you can keep them both unchecked if they are already
unchecked by default)
However, if you use firefox, console shows the error: "Uncaught out of memory"
Here, I got the first hint. Firefox at least told me to look at memory, but it is not about the memory we think. It is not about multiple tabs opened, lack of disk space, unstable disk, etc. It is the accidentally generated infinite loop in the code which is causing the memory problem (check your code carefully to find it).
In my case, I accidentally didn't tell it to execute the next iteration (i.e., missing counter update, increment, i++) and it is stuck in the same while loop forever, as the condition is satisfied forever without any counter update.
After fixing the code, the below error might show up in the console. Just refresh the page and it will go away.
"favicon.ico:1 Failed to load resource: the server responded with a status of 404 (Not Found)"
Note: Unless you fix the code or comment it out, other linked files (like .html) in the folder wouldn't work either.

Getting browser popup message error when executing any cells on Google Colab

I am unable to use colab. I was executing a notebook when I have received a popup message error saying:
Error
Could not load the JavaScript files needed to display output.
This is probably because your Google account login access has expired or because third-party cookies are not allowed by your browser.
Please reload this page.
DETAILS
I'm using Google Chrome version 80.0.3987.149
I have tried to restart runtime, reloaded the page, tried to execute notebook in incognito window, restarted the browser and it did not work.
So, I tried to use Mozilla Firefox and Microsoft Edge and the error kept showing. Further, I changed my Google account, I tried 3 differents accounts and it didn't work.
I also allowed [*.] googleusercontent.com cookies in the Allow section and the third-party cookies are enable.
well I had the same problem and tried all the things you tried and more crazy solutions but none worked , the magic thing that worked in the end was to open colab using any vpn !

Angular (7.2.10) app failing to load on Chrome on iOS 12.4.1

I'm currently working on an Angular application (7.2.10) and on the latest version of iOS available on my device (12.4.1) we have hit an issue that I can't seem to figure out. The issue only occurs on Chrome on iOS, I am unable to replicate this issue on any other browser on the affected devices. The iPad air (1st gen) I am running against is using Chrome version 77.0.3865.93. It was first reported by a colleague using an iPad Pro, and we have has a couple of clients call in saying it's not working on their iPhones.
If we load the entry point to our web application (https://ams.invenias.com) the screen is completely blank. Nothing loads, and the spinner stops immediately.
I've tried a few avenues to try and get to the root of the problem, but I am yet to get anywhere. I have...
Using ios-webview-app to run iOS simulator within safari on a mac. This just resulted in the website loading as normal, so something wasn't being simulated correctly.
ios-webkit-debug-proxy to attempt to get developer tools in chrome for iOS. This ended up not working at all, either I was unable to get it running or our particular network setup meant it would never work.
Using weinre to get some sort of developer tools to read network activity/logs. I wasn't able to get this running initially, however after a bit of tinkering I was able to use this alongside Browserstack to get developer tools. Unfortunately, nothing in the logs or DOM was erroring or showed any reason as to why it might not be starting correctly.
After connecting via number 3, I was able to find out that angular itself is not bootstrapping, and no javascript is being executed on the page (from within the transpiled code, javascript included in other .js files, or within index.html executes correctly.) I'm now on day 3 with this issue, and no end in sight.
Oddly enough, if we use the 'Request Desktop Site' feature within the browser, the site loads perfectly.
Thanks,
Cameron

Script doesn't change after deploying site on Firebase. Same error persists

I have a website that is hosted by Firebase on which I badly commented some lines of code. That code has been fixed and deployed but the problem persists.
I changed an aspect of the HTML to see if the website gets deployed at all whenever I tell it to and that changed in a few seconds. The error is still there though and if I go in the console and click on the line the error should be on it still shows me my old script which is now fixed.
code my error points to(this is what it actually looked like about 5 deploys ago): https://imgur.com/a/TmA29tP
actual code (removed the comments) (/public/assets/js/login.js): https://imgur.com/a/3pyjTwd
I expected the error to go away after deploying as the site is actually updating its files as I saw after testing it with the HTML element but all I get is the login.js:56 Uncaught SyntaxError: Unexpected end of input error because the comment is badly placed.
EDIT: This solution worked for me: Disabling Chrome cache for website development
it is likely because you need to hard refresh (e.g. bust cache) to see your new site.
In chrome, there is an option to disable caching while you have dev tools open. You should enable that option, refresh the site with dev tools open, and see if your problem persists.

Chrome javascript errors

Google Chrome started to show errors in the console. The page is just a regular PHP page that has one function echo 'a';. I have attached a screenshot of the errors. Google Chrome
Seems to be an issue with some Chrome extensions, not with the page itself. Maybe update them, remove them or just ignore them.

Categories