notFound generates critical error with i18n

[GeorgeHulpoi]

Link to the code that reproduces this issue

https://github.com/GeorgeHulpoi/nextjs-not-found-bug

To Reproduce

1. Go to http://localhost:3000/de and you will see the following errors in console:
   

Current vs. Expected behavior

When the notFound is called from next/navigation, seems to produce the error. Normally, it should show the default 404 page.
For example, navigating to http://localhost:3000/en/test render the default 404 (as expected).

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
  Available memory (MB): 14189
  Available CPU cores: 16
Binaries:
  Node: 20.9.0
  npm: 10.1.0
  Yarn: 1.22.21
  pnpm: 9.15.0
Relevant Packages:
  next: 15.1.2 // Latest available version is detected (15.1.2).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: N/A
Next.js Config:
  output: N/A

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

Internationalization (i18n), Navigation

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

next dev (local), next build (local), next start (local)

Additional context

Related issues:
#59180
#55191

I followed the steps from https://nextjs.org/docs/app/building-your-application/routing/internationalization ;