You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a winit screen is launched and screen is turned off by xset dpms force off, memory consumption of awesomeWM starts to rise unusually and eventually cause Linux OOM killer to kill awesomeWM. This issue exist even if the winit client is not rendered on screen.
This issue is resolved when window shape decoration code is commented out (line 561 to line 567 in the config).
Memory usage could be reduced by forcing Lua to do a GC. I thought winit was causing unnecessary manage signal emitted but that was not the case. The signal was not emitted when screen is off.
I was launching an example winit window by the following example code:
Related issue: alacritty/alacritty#2004
winit version:
0.18.1
Under X11 with awesomeWM 4.2. Winit would cause awesomeWM to memory leak when client shape decoration is enabled in awesome's end.
Minimal awesome configuration
When a winit screen is launched and screen is turned off by
xset dpms force off
, memory consumption of awesomeWM starts to rise unusually and eventually cause Linux OOM killer to kill awesomeWM. This issue exist even if the winit client is not rendered on screen.This issue is resolved when window shape decoration code is commented out (line 561 to line 567 in the config).
Memory usage could be reduced by forcing Lua to do a GC. I thought winit was causing unnecessary
manage
signal emitted but that was not the case. The signal was not emitted when screen is off.I was launching an example winit window by the following example code:
The text was updated successfully, but these errors were encountered: