New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chrome sends thousands of requests in few seconds and does not stop #176
Comments
I noticed the same once in Nuxt as well, but can't reproduce either. This is probably a bug, but I guess I will need more information to find the root cause and fix it. Leave the comment below and share your reproduction steps or any more context if you also faced the same. Thanks a lot! |
I get this intermittently, but it resolves itself eventually - normally after restarting |
When I gave my colleague my project address and then modify the "vite.config.js" server.proxy.target configuration,wait for the Vite to restart automatically, This bug is 100% recurring.
|
same here, when I gave host url to another colleague, both accessing the url, then the requests just went from hundreds to thousands and way more, memory, cpu usage went up like crazy...the site was frozened, even Chrome itself started to showing signs of crashing... And I'm using 16'' Macbook... I tried use localhost instead of Is there some kind of loop here? |
I think this basically happens whenever you connect to the same vite server twice through different domains (localhost, 127.0.0.1). I get this exact issue whenever I use an iframe or use my phone and visit my localhost through my network adres. |
This happened to me few times the last days, just three times today. I cannot reproduce it reliably, so feel free to close. I still thought, it might be good to let you know.
Sometimes, my browser starts to dispatch thousands of requests in few seconds and does not stop. Reloading, loading in a new tab, restarting docker-compose, all together does all not help, initially. At some point after I did all of the aforementioned things a few times and waited things got back to normal.
This happened with SvelteKit@next in dev mode.
Inspectors' Netowrk tab looks like this:
The text was updated successfully, but these errors were encountered: