Global error handler (global-error.tsx) fails to catch errors in nested layouts

[SiarheiLazakovich]

Verify canary release

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

Provide environment information

Operating System:
      Platform: linux
      Arch: x64
      Version: #22 SMP Tue Jan 10 18:39:00 UTC 2023
    Binaries:
      Node: 16.17.0
      npm: 8.15.0
      Yarn: 1.22.19
      pnpm: 7.1.0
    Relevant packages:
      next: 13.4.4-canary.0
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 4.9.5

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

No response

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

https://codesandbox.io/p/sandbox/runtime-water-ylwcg0

To Reproduce

1. open: https://codesandbox.io/p/sandbox/runtime-water-ylwcg0
2. execute: yarn start (or yarn && yarn build && yarn start)
3. see:

Describe the Bug

After upgrading to version v13.1.7-canary.11 and newer, the global error handler (global-error.tsx) fails to catch errors that occur within nested layouts. When an error occurs in a layout, the global error handler is not triggered, and the error is not handled.

Expected Behavior

When any error occurs in the application, the global error handler (global-error.tsx) should be triggered regardless of the level of nesting in the layouts. The global handler should catch and handle errors at any level of layout nesting.
Same as was in 13.1.7-canary.10.

codesandbox with 13.1.7-canary.10: https://codesandbox.io/p/sandbox/crazy-lake-nw0qy7

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

[RafalChojnowskiPagepro]

For me it doesn't catch error from root layout either

[llee1990]

Still seeing this issue after upgrading to v13.4.10. Unable to catch errors from root layout. Only from root error.tsx

[KristineTrona]

Same here, updated to 13.4.10 and throwing an error in root layout does not display global-error.tsx

[subalee]

Same here @13.4.11

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.