-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Linux/X11: crash on 0.85.0+ when trying to show a tooltip from title
attributes ("GPU process exited unexpectedly: exit_code=133")
#8184
Comments
Also note that the crash let some rendering process alive and orphaned, eating quite some bunch of cpu/gpu resources. |
I couldn't reproduce this on macos running on apple silicon. The tooltips look fine. I only tested macos though. |
I also got a nvidia and use X11 |
I can confirm that the problem is also present when running: |
I was going to open a similar post. Game created with the game engine Construct 3, exported for Linux with NWjs versions from 0.85.0 until latest, closes the window straight away once launched. Tested on Linux laptop:
Post about the issue on Construct 3 forum and got a reply from one of the software creator where he suggested to report the issue here: |
I can confirm that the problem with the title tag for tool-tips, and hanging processes is solved with version 0.92.0. Running on: |
Issue Type
Before opening an issue, please search and see if it has already been raised.
Bug Report
Feature Request
Successfully reproduced against the latest version of NW.js?
Issue
Reproduction: https://github.com/bastimeyer/nwjs-tooltip-crash
Related: streamlink/streamlink-twitch-gui#1005
When using NW.js
0.85.0+
, including the latest version0.87.0
with Chromium 124, the GPU process crashes when the application tries to render a tooltip from anytitle
attribute in the DOM tree. This is not the case on0.84.0
and below.The GPU process crash seems only to happen when using Chromium's X11 ozone platform implementation. This is still the default on Wayland without the
--ozone-platform=wayland
arg being set explicitly (unfortunately).Apparently, the issue also does only occur when using an Intel or Nvidia GPU. I couldn't manage to reproduce this on my main system using the AMDGPU kernel driver and latest mesa. In the issue report on my application, only reports from users with Intel or Nvidia GPUs have been made so far.
Here's an error log from my notebook running KDE Plasma on Wayland using an integrated Intel GPU (i915 kernel driver + latest mesa). As said, the issue does only occur on X11 / XWayland.
The text was updated successfully, but these errors were encountered: