SSR sometimes breaks utf8 characters in component props into individual bytes

[vadzim]

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: #1 SMP PREEMPT_DYNAMIC Mon Feb 6 11:26:13 UTC 2023
Binaries:
Node: 19.6.0
npm: 8.19.2
Yarn: 1.22.19
pnpm: N/A
Relevant packages:
next: 13.2.2-canary.3
eslint-config-next: 13.2.1
react: 18.2.0
react-dom: 18.2.0

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

App directory (appDir: true)

Link to the code that reproduces this issue

it reproduces randomly

To Reproduce

Render a "use client" components with props containing utf8 characters.
Sometimes utf8 characters are broken like that:

:I{"id":"(app-client)/./src/app/[lang]/login/Login.tsx","name":"Login","chunks":["app/[lang]/login/page:app/[lang]/login/page"],"async":false}\n9:["$","$La",null,{"lang":"ru","translations":{"sign_in":"Увайсьці","email_address":"Адрас e-mail","password":"Пароль","forgot_password":"Забыліся парoль?","remember_me":".За�"])</script><script>self.__next_f.push([1,"�омніць мяне"},"children":["$","$Lb",null,{}]}]\n"])</script>

Actually the broken string should be Запомніць мяне

Describe the Bug

The bug is in the use of the function decodeText in app-render.ts file.

The function decodeText has the second argument which should fix utf8 characters support, but it's not used in app-render.ts.

To not break utf8 characters the second argument to decodeText should be always provided.

Expected Behavior

Utf8 characters are not broken

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

[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.