Link to the code that reproduces this issue

https://github.com/MOSAIC-ETC/website

To Reproduce

1. Start the application in development mode (next dev)
2. Go to a non-existing page (/404, for example)
3. Make a change in the code of [locale]/not-found.tsx (change the text)
4. Update the page some times
5. If it doesn't work, go back to step two, after some time (not very long, but it is somewhat random), it should appear

Current vs. Expected behavior

The error shouldn't happen.

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Tue Nov 5 00:21:55 UTC 2024
  Available memory (MB): 15893
  Available CPU cores: 16
Binaries:
  Node: 22.18.0
  npm: 11.6.2
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 16.0.2-canary.16 // Latest available version is detected (16.0.2-canary.16).
  eslint-config-next: N/A
  react: 19.2.0
  react-dom: 19.2.0
  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'm using WSL.

The error has something to do with the CatchAllPage that shows the NotFound component. The error may show outside a not-found page, and it shows randomly (but frequently) during development when i'm making changes to the code. I didn't find anything related to cannot have a negative time stamp anywhere else.