Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexpected exit of renderer process #1

Open
YukariChiba opened this issue Apr 22, 2024 · 5 comments
Open

Unexpected exit of renderer process #1

YukariChiba opened this issue Apr 22, 2024 · 5 comments

Comments

@YukariChiba
Copy link

Environment

deepin v23 on loong64 with qt6-webengine 6.6.3, latest patch included.

Reproduce

  1. Install deepin v23.
  2. Install qt6-webengine-examples
  3. Run /usr/lib/loongarch64-linux-gnu/qt6/examples/webenginewidgets/simplebrowser/simplebrowser
  4. An error would appear: Render process exited with code:5
@jiegec
Copy link
Member

jiegec commented Apr 22, 2024

Environment

deepin v23 on loong64 with qt6-webengine 6.6.3, latest patch included.

Reproduce

1. Install deepin v23.

2. Install `qt6-webengine-examples`

3. Run `/usr/lib/loongarch64-linux-gnu/qt6/examples/webenginewidgets/simplebrowser/simplebrowser`

4. An error would appear: `Render process exited with code:5`

Thanks for reporting, I am trying to reproduce the problem.

@jiegec
Copy link
Member

jiegec commented Apr 22, 2024

I have reproduced the bug:

(gdb) bt
#0  0x00007fffe65662f0 in v8::internal::Deserializer<v8::internal::Isolate>::Deserializer(v8::internal::Isolate*, v8::base::Vector<unsigned char const>, unsigned int, bool, bool) () from /lib/loongarch64-linux-gnu/libQt6WebEngineCore.so.6
#1  0x00007fffe656628c in v8::internal::Deserializer<v8::internal::Isolate>::Deserializer(v8::internal::Isolate*, v8::base::Vector<unsigned char const>, unsigned int, bool, bool) () from /lib/loongarch64-linux-gnu/libQt6WebEngineCore.so.6
Backtrace stopped: frame did not save the PC

@jiegec
Copy link
Member

jiegec commented Apr 22, 2024

Seemed like some memory corruption... You can try updated patch from 0e0582e, but I am not sure if it is the problem.

@YukariChiba
Copy link
Author

Seemed like some memory corruption... You can try updated patch from 0e0582e, but I am not sure if it is the problem.

Verified, NOT work.

@jiegec
Copy link
Member

jiegec commented Apr 23, 2024

Seemed like some memory corruption... You can try updated patch from 0e0582e, but I am not sure if it is the problem.

Verified, NOT work.

Then I have no idea.. And it is not reproducible on AOSC OS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants