-
Notifications
You must be signed in to change notification settings - Fork 22
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
Random crashes in ca. 1min to 1h on Intel laptop with igpu driver (Iris) calling abort() / SIGABRT #25
Comments
Considering it crashed at: Lines 141 to 144 in 666f4c9
And didn't just throw back an error message. I want to say mpvpaper didn't do anything wrong here. Also, it went from having a pointer to the display, to not? But I'm not a graphics expert, go ahead and take this upstream. Thank you for your excellent debug logs and effort! |
I'm closing this because since mpvpaper commit 781320f this crash is extremely rare (happened only once for me since) and thus not reproducible. (For the record: the crash likely happened with two Iris driver I915_GEM_EXECBUFFER2 ioctls which by random chance came within ~5us close in time, caused one of them to fail with errno ENOSPC which Mesa chooses to abort on. The leading cause to this event remains unknown, and could be anywhere in the whole application + libraries. The Mesa issue I reported is here although Mesa devs were not really interested.) Moreover a week ago I saw a similar backtrace for a vanilla mpv crashing. Likely this situation was not and is not mpvpaper's fault. |
Thank you for your investigation into this issue! |
Hey, first of all thanks for the recent patches.
I was hoping it will solve some random crashes of mpvpaper I had in the past half year, but sadly things didn't change for me.
cpu/gpu: Intel i5-1035G4 (10th gen mobile)
display: external HDMI monitor to laptop
system: Arch Linux
wm: Sway
mpvpaper: reproduced both on 1.2.1 and current master branch
mesa: reproduced both on 22.1.7-1 and current main branch
kernel: reproduced both on 5.19.7.arch1-1 and current drm-tip
In the coredump all the crashes all traced as abort() < iris_dri.so < libEGL_mesa.so < render() at ../src/main.c:142 :
I attach the coredump and the gdb debugging session with (gdb) thread apply all bt full
coredump-gdb-analysed.txt
core.mpvpaper.1000.6f0499264a6a4d699984290d77c2b318.11720.1662816696000000.gz
I would like to ask your opinion as if this is likely a mpvpaper issue or likely a Mesa issue?
If the later, then do you think I should I go ahead and report it on Mesa issues as an Intel igpu driver (Iris) bug?
(potentially pointing Mesa devs to mpvpaper to reproduce it?)
The text was updated successfully, but these errors were encountered: