Freeze when using Link component to a custom not found page

[mlazuardy]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.4.0: Mon Mar  6 20:59:28 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.14.0
      npm: 9.3.1
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.4.3
      eslint-config-next: 13.4.3
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.0.4

Which area(s) of Next.js are affected? (leave empty if unsure)

Routing (next/router, next/navigation, next/link)

Link to the code that reproduces this issue or a replay of the bug

https://github.com/mlazuardy/nextjs-starter

To Reproduce

run app in dev mode

on the main page, click the Docs link which is changed to the /not-found-page url

Describe the Bug

when using Link component and navigate to not found page, the app freezed except we reload the browser

it only happened when using custom not-found.tsx file inside app/not-found.tsx`

Expected Behavior

should navigate and return a custom not found page

Which browser are you using? (if relevant)

Chrome 113.0.5672.126

How are you deploying your application? (if relevant)

Local

[PassTheMayo]

Experiencing the same issue on Next.js 13.4.3 as well. The browser will push the URL to the stack (updating the URL in the address bar) but does not re-render the page. Refreshing causes the correct 404 page to be rendered, but navigating away from this 404 page results in the same issue unless you refresh again.

[shubh140601]

Same issue 13.4.2

[joshtinhan]

This issue was fixed in v13.4.4 See the PR #50047