WSLg Crashes Randomly due to multi-thread race condition to access RDP id_manager #678
Labels
Comments
|
seems to be the same as #589 |
|
@manuth, please update WSL to the latest version from aka.ms/wslstorepage, and if this still occurs after update, please share core dumps from /mnt/wslg/dumps, thanks! |
I'm running the most recent version of WSL Thanks for your help 😄 |
|
I'm having a similar issue. Today I faced it twice. All wslg apps suddenly crash and can not be started again until the wsl subsystem is restarted. I've collected wsl logs but don't want to expose them publicly. |
|
@speller, do you see any dumps at /mnt/wslg/dumps? and please make sure the WSL is the latest by |
|
Here are some logs from inside WSL:
|
|
@hideyukn88 |
|
@speller, would you please share with us? if you are uncomfortable to share here, you can send us using Feedback Hub, please select below category and including the link to this page at description, thanks!
|
|
@hideyukn88 I've created the feedback hub issue but can't get a web link. Only the internal uri is available: feedback-hub:?contextid=677&feedbackid=f1c8c805-a43e-4c02-92dd-20015507238b&form=1&src=1 |
|
I've attached WSL logs collected from under Windows and the dump. Relevant pieces of wslg logs are already posted here. |
|
@speller, thank you very much for sharing the dump, For reference, below is the callstack for the crash and I will work on the fix, thanks again for reporting the issue! |
hideyukn88
changed the title
|
@hideyukn88 thank you for the prompt response! Will wait for the fix. |
|
@hideyukn88 By the way, is there a quick workaround to restart the graphics subsystem without restarting the whole WSL? |
2 tasks
|
@hideyukn88 when this fix is planned to be released? |
|
@hideyukn88 is the issue still not pending to be merged? I've faced a very similar issue |
|
The error happened at 18:27
I tried to run a program after the crash, but nothing displayed on the screen while there is an activity in the weston log. Feedback ID with the core.weston dump: feedbackid=2f6d616d-7dac-4e1e-842c-520700ce0bfa After shutting wsl down and restarting, GUI started working again. |
|
@speller, is this your feedback? https://aka.ms/AAjtxhz, thanks! |
|
Note to self:
[18:27:50.818] RDP clipboard_data_source_send new (0x7f56cc000e50:published:fd 110) vs prev (0x7f56cc000d40:cancel pending:fd 109): outstanding RDP data request (client to server)
Program terminated with signal SIGSEGV, Segmentation fault. (gdb) info local (gdb) print *source Thus source->data_source_fd is already writable when below is executed, so clipboard_data_source_fail is called prior to event_source pointer is written to source->transfer_event_source, but at time of dump is captured, the write is done as above shows non-null pointer, while callstack has null pointer. ret = rdp_event_loop_add_fd(loop, source->data_source_fd, WL_EVENT_WRITABLE, |
|
@hideyukn88 yes, it's mine. Do you need a separate ticket for this issue here on github? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
Steps to reproduce
virt-manager)WSL logs:
/mnt/wslgYou can access the wslg logs using explorer at:
\\wsl$\<Distro-Name>\mnt\wslg(e.g.:\\wsl$\Ubuntu-20.04\mnt\wslg)pulseaudio.logweston.logversions.txtstderr.logExpected behavior
The GUI should at most lag.
Actual behavior
All GUI applications immediately close.
Following lines are written to the
stderr.logwhen this happens:The text was updated successfully, but these errors were encountered: