nextjs - 💡(How to fix) Fix App freezes after back navigation when visiting route via manual URL [2 comments, 2 participants]

Link to the code that reproduces this issue

https://github.com/JulienB18/nextjs16-back-issue

To Reproduce

1. Install the app and start it in development mode (next dev)
2. Click on the button ("Click button") → an alert is displayed
3. Go to the login page by manually typing the URL localhost:3000/login
4. Go back using the browser back button and click the button again ("Click button") → the alert does not appear anymore
5. Refresh the page → click on the button ("Click button") → an alert is displayed
6. Click on the button ("Go to login page")
7. Go back using the browser back button and click the button again ("Click button") → the alert is displayed again

Current vs. Expected behavior

Here is a video where I reproduce the bug

https://github.com/user-attachments/assets/87c94add-0a04-4737-a78c-44a3fd4e3395

The expected behavior is that when I manually navigate to the login page and then go back using the browser back button, the JavaScript should not freeze and the buttons should continue to work normally. If you put an useEffect(() => {console.log("test")}, []); it will not work too after the back.

If you navigate to the login page using a router push and then go back using the browser back button, everything works correctly.

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 32599
  Available CPU cores: 28
Binaries:
  Node: 22.15.1
  npm: 11.6.2
  Yarn: N/A
  pnpm: 10.21.0
Relevant Packages:
  next: 16.2.4 // Latest available version is detected (16.2.4).
  eslint-config-next: N/A
  react: 19.2.4
  react-dom: 19.2.4
  typescript: 5.9.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Not sure

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

I got the bug on Chrome and Firefox. I tested my reproduction on NextJS v15.5.15 and I dont have this bug.