I'm trying to debug my app that is built with Vue 3 and Vite, it should work fine, it works to debug with firefox, (but is far from ideal since firefox don't remember settings once closed, etc), but with chrome when I hit F5 while debugging, it will never refresh, it gets stuck loading. Any ideas why this may be happening?
Related
I have some weird thing going on in my machine. When loading a specific website at work and opening the Chrome devtools, the website's tab gets frozen, Chrome task manager shows > 100% CPU usage and all is frozen and unusable.
I’ve tried the following, none worked:
Disabled all extensions
Cleared cookies
Restarted Chrome
When loading the same URL with devtools in Incognito mode, all is splendidly working and smooth as butter.
What can be the problem here? I'm using Chrome version 79.0.3945.130, which is currently the latest
I am running Node.js on localhost:3001 and unintentionally wrote some code with an infinite while loop. This locked up Chrome to the point where the only resolution was to kill the browser. Since then, I found the problem in my code using Firefox, and fixed the code, but even after restarting Chrome, it will not load my page. I even changed the port that the server runs on, and the cache is disabled with developer tools open - Chrome simply refuses to load the page. I see a single request to the server for the page, but in Chrome it just registers as Pending.
Has Chrome maybe flagged this page as suspect, somehow? How do I get it to play again? I would at least expect Chrome to offer some opportunity to kill a tight loop - like Firefox does - but I've yet to see it. Is there some setting I can tweak? I'm on version 74.0.3729.169 (Official Build) (64-bit), although now that I opened the About page, I see that it is updating Chrome, so maybe that will fix it.
UPDATE: It didn't fix it, but it works in Incognito mode. ???!!!
UPDATE: Disabling all of my extensions also didn't fix it!
I found a setting in Chrome: "Continue to run background apps when Chrome is closed"
I turned that off, and now it works again.
The same application that I am developing works fine on Firefox but not on Chrome.
My application a day ago printed some things on the console, but I removed them today, which means that the actualized version of the application does not print anything on the console.
On Firefox it works, everything renders and there is not prints on the console.
However on Chrome, the app still prints on the console. It means that it is retaining some old state for some reason.
Does that even make sense? The code is already gone (erased), so the only way Chrome is printing the old state on the console is if he is storing it.
On Chrome I also get errors of undefined functions, but they are defined. On Firefox that does not happen.
Have you tried reloading the page? Another thing to try to really get rid of the state that the browser is obviously holding onto is to clear the browser cache.
I have a simple web page running locally on my machine using XAMPP.
When in Chrome and I load the page, the page appears to load fine and appears as expected. The icon in the tab continues to show the spinning "loading" icon though, it never stops.
Using Chrome Developer tools I can see the network tab and there is nothing showing as loading
Also if I use Internet Explorer then the page loads and there is no loading icon.
Any idea why Chrome might think it is still loading something?
I had the same problem and found out it was one of my chrome extensions. I tried loading my site in an incognito page and the loading symbol stopped after the page finished. I went through my extensions to see which were not allowed in incognito and eventually found that it was "Mailto: for Gmail™ 2.4" causing the problem.
For what it's worth after eight years, I had a similar problem where Chrome would not load some images even though they were definitely available, ready, and waiting.
My solution was to close the browser, flushing cookies, history, and all the other internal cruft which had built up over time (using the "Close All & Clean" extension).
Restarting the browser and reloading the page, everything was there, all tickety-boo.
I have no useful theories on why this might've worked but as they say "works for me." Your mileage may vary.
I have an razor MVC page - It is loaded via MVC Portable Areas.
When i browse to the index action, everything loads fine, and works as expected.
...But occasionally Internet Explorer continually shows the loading bar in the status bar. The loading never completes, but the page functionality works fine (so it must have loaded all my resources)
I can't replicate this in firefox, and i have checked the Net tab on firebug to look for slow loading resources, but everything looks fine.
I want to try and cause the loading bar to stop after a set time (i know this could be masking a problem, but i can't seem to find out what is going wrong with the page!!)
Is there a way to do this?
IE does that sometimes. Like you said, there is no actual issues except for the loadfing bar being shown.
To confirm that everything is OK, put an alert("loaded") in your $(document).ready();. If it alerts you, the page was successfully loaded and it's just IE being a buggy little... bugger.
Edit: I missed a bit. Continued:
This is ofcourse only the case if you do not have ajax calls etc on the page that can start a loading sequence after the document has loaded. In that case, use the debugger to check for open connections.