Chrome hanging after multiple refreshes when only one tab is open
See original GitHub issueBug report
Describe the bug
When using now dev, I sometimes get the multiple tabs warning and application hangs even though only one tab is open.
To Reproduce
This happens most frequently when I have the debugging console open and do a browser refresh.
Expected behavior
Expect the application to refresh.
System information
- OS: OS X 10.14.4
- Chrome 74.0.3729.131 (Official Build) (64-bit)
- Version of Next.js: ^8.1.0
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Chrome hanging after multiple refreshes when only one tab is ...
When using now dev , I sometimes get the multiple tabs warning and application hangs even though only one tab is open. To...
Read more >Chrome tabs intermittent hang or crash with white screen
Issuing input to the browser, such as reloading the pane or opening a new tab, gets the expected result. An immediate fix to...
Read more >How to Fix It When Chrome Keeps Freezing - Lifewire
Restart Chrome. This simple troubleshooting step often solves the problem. Close all Chrome tabs and windows, wait a few minutes, and reopen ......
Read more >Chrome Tabs Keep Refreshing – What To Do - Alphr
Open a new Chrome tab. · Now, locate the Auto Discardable column and click on Toggle under the checkmark of the tab you...
Read more >Chrome Tabs Keep Auto-Refreshing? Here's How to Fix It
Launch Task Manager and close any background process that Chrome is still running.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

No problem.
nowdoesn’t register a service-worker either so there might have been another application that usedlocalhost:3000that registered one at some point that didn’t get cleaned up. I usually develop in incognito mode to prevent stuff like that.Next.js doesn’t register a service worker so this is probably a stale one that was never cleared. You can clear it under the
Applicationtab in the Chrome dev tools. I’m gonna close this now since that appears to be what was causing the issue.