Skip to content
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

Slow page reload running in development #25108

Open
bjrb20 opened this issue May 13, 2021 · 6 comments
Open

Slow page reload running in development #25108

bjrb20 opened this issue May 13, 2021 · 6 comments
Labels
bug Issue was opened via the bug report template. good first issue Easy to fix issues, good for newcomers

Comments

@bjrb20
Copy link

bjrb20 commented May 13, 2021

What version of Next.js are you using?

10.2.0

What version of Node.js are you using?

14.15.4

What browser are you using?

Chrome

What operating system are you using?

macOS

How are you deploying your application?

n/a

Describe the Bug

When running npm run dev if you reload the page (refresh) a few times, after about the 5th refresh the load time gets very slow and almost unusable.

Expected Behavior

Refresh should be less than a few seconds.

To Reproduce

npx create-next-app app
cd app
npm run dev

Refresh the page 5-10 times.

@bjrb20 bjrb20 added the bug Issue was opened via the bug report template. label May 13, 2021
@mazc28
Copy link

mazc28 commented May 17, 2021

Im having the exact same issue, but I can add some other things to take into consideration:

It gets stucked even when you dont manually refresh, after approximately 5 minutes using it with hot reloading or 5 minutes of inactivity. Sometimes it doesnt even work to kill the process and start it over and I have to do it repeatedly until it works.
I have tested using it with NPM and YARN as well, and running "next dev" or only "next", deleted cache and node modules and install it again but no luck so far.

im using the exact same versions of the tools but working on Windows 10.

@Blessen
Copy link

Blessen commented Jun 4, 2021

+1

@mazc28
Copy link

mazc28 commented Jun 4, 2021

I have found a solution, dont know if its permanent, but here it is. Im using windows tho, so what I did was created an exclusion on windows defender directly on the project's folder and that was it. Windows defender may be causing this delay because of a deep scan it performs on some files within the folder, hope it can help someone.

@jankaifer
Copy link
Contributor

I was unable to repro this but I'm on Linux.
We will probably not dig into this so If anyone from the community is interested we would love to assist you in finding the root cause and review your PR with a fix.

Thanks mazc28 for finding out the thing with Windows defender.

@jankaifer jankaifer added good first issue Easy to fix issues, good for newcomers type: needs investigation labels Nov 29, 2022
@isaackatayev
Copy link
Contributor

Can you link an example?

@zarelloshake
Copy link

I encountered the same problem as you described, and following mazc28's suggested solution, I was able to successfully resolve the issue on my Windows 11 system (Node.js v18.20.5). Thank you guys very much for sharing this probem and solution, it's very helpful for me a newbie.

If anyone encounters the same problem in a similar development environment, the following troubleshooting steps may be helpful:

  1. Open the Windows Security app.
  2. Click on "Virus & threat protection" on the left.
  3. Under "Virus & threat protection settings", click on "Manage settings".
  4. Scroll down to the "Exclusions" section and click on "Add or remove exclusions".
  5. Click on "Add an exclusion", and select "Folder".
  6. Navigate to the folder where your Next.js project is located, then click "Select Folder".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue was opened via the bug report template. good first issue Easy to fix issues, good for newcomers
Projects
None yet
Development

No branches or pull requests

7 participants