Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
High `next dev` memory usage on elementary OS
See original GitHub issueBug report
Hi, I’m developing a project for the next@9.0.5 and I’ve encountered a problem as I mentioned in the title. I’ve shared detailed information below
Describe the bug
If there is a browser with the local address where your application is published, nodejs starts to use your machine’s memory in seconds. I’ve removed all plug-ins, components, and pages from within the project to solve the problem, but none has been resolved. What I noticed is that if the website is not open on any browser, it uses memory properly (around 300MB), but this problem arises when you turn off the giant server and turn it on again. I didn’t come across this problem when NextJS was first installed.
Screenshots
System information
- OS: elementary OS 5.0 Juno (Ubuntu 18.04.2 LTS)
- Browser: Chrome Version 77.0.3865.90 (Official Build) (64-bit)
- Version of Next.js: 9.0.5
Additional context
It seems that there is no problem with the Windows Operating System.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@jeremy-coleman I’m not sure how your comment here is relevant. You didn’t investigate the issue outlined here: https://github.com/zeit/next.js/issues/8808#issue-496374488.
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.