-
-
Notifications
You must be signed in to change notification settings - Fork 942
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
Sigh unsafe stuff take 3 #3713
Sigh unsafe stuff take 3 #3713
Conversation
no worky for me. Nothing changed compared to before. |
Now it crashes for me. I just had lxappearance, xeyes, waybar, and vscode open.
|
can you do https://wiki.hyprland.org/Crashes-and-Bugs/#building-the-wayland-stack-with-asan ? I know it's tedious but this seems like a memory issue |
Can't build hyprland:
|
oops. Sec. |
a59792f
to
f48e81b
Compare
should be fixed. |
It doesnt let me start xwayland programs, so I can't cause a crash, but here's the log for waybar on reconnect:
I get address boundary error when starting xeyes or any other xwayland thing |
what if you manually start xwayland from a terminal with the ASAN env? Also maybe you forgot the |
I started xwayland and got a crash immediately I did put the ASAN_OPTIONS in my config |
good, means it's working. Post an asan log just like in the directions :) |
Log
|
top! fixed. Rebuild with asan and do the same. Rinse and repeat. Post logs until there is no crash :) |
do I checkout unsafe blah blah or nah |
stay on this MR, just |
I cant build:
nvm im dumb |
ok Xwayland doesn't crash but waybar still does, same error And now opening xeyes gives: |
open xeyes with What about the sleep/hibernate/whatever crash? |
No sleep crash yet |
I'll let @rszyma report back then after the latest commit |
I tried building in normal debug and it looks like it's fixed, but it spawns my mouse outside of the workspace that I reconnect on. It fixes it when I drag it back from the void. Also I think the right mouse boundary of the screen broke, it's causing some weird bugs with the workspaces |
lolwut, can you check |
ye it does, i guess it's treating it as a second monitor |
oopsie daisy >////< |
can you grep the log and check whether the |
Got nothing. |
That's what I'm doing right now. Should I try with asan? |
no, hm, odd. You were supposed to launch hyprland normally where xwayland worked? like you could launch x apps? You should launch exactly in that state, with only adding the aforementioned env to the cmdline |
Yes I just launched into my main build (on 99d7e47) with the WLR_XWAYLAND thing. I ran the script from the terminal instead: |
thanks, that helps |
@phonetic112 @rszyma xwayland crash should be fixed. Please test. |
@vaxerski seems to be working for me so far! Put the computer to sleep with Waybar and Steam active and upon waking, everything was as it was before. Same with locking screen and turning monitors off |
great, I'll wait for @rszyma and if they give an ok I'll merge this and close the original issue |
It still crashes for me, nothing running except two alacritty terminals: hyprlandCrashReport15017.txt I don't have an asan-enabled build and can't easily follow the instructions in the wiki because nixos. |
Fixed with this patch: update-all-outputs-patch.txt |
Waybar itself crashes for me (not too problematic since it's restarted by systemd), could be a bug in Waybar itself. Hyprland has not crashed so far and neither any other app that crashed before (on xwayland or electron). Waybar crashes here: https://github.com/Alexays/Waybar/blob/master/src/modules/hyprland/workspaces.cpp#L297-L311
Maybe because Hyprland is returning |
Same for me. Identical crash log. Just waybar or xeyes enough to cause the crash.
I tried this patch too, and it seems to fix everything! Including waybar. |
I found a different issue with xwayland, maybe related to this the previous ones that this PR adresses:
Result: It happens only with xeyes, and only after a suspend/wakeup cycle. Should I create a new issue instead of blocking this PR? |
If waybar is not crashing for you I assume you're not using the monitor-undefined-json-patch.txt This patch helps with the waybar crash, but it crashes elsewhere now (when processing |
right, missed nullcheck my bad! Please check now |
yep, not using |
Can you also include this patch? Otherwise we return invalid JSON ("undefined" is not a valid JSON type). |
done |
Since issues are solved, I'll merge this |
not entirely sure if related to this change or not, but since pulling this in, having swaylock segfault after resume when display is turned off
|
if it helps |
Stuff
re: #3637