Open database64128 opened 3 days ago
This likely affects the Meteor Lake (MTL) platform as well, since Arrow Lake S CPUs use the same generation of iGPU as Meteor Lake (MTL) CPUs.
Crash in
intel-media-driver
I think reporting it to them would be more appropriate, mpv can't really fix a null pointer deref on this
in C++ code deep within intel-media-driver.
Crash in
intel-media-driver
I think reporting it to them would be more appropriate, mpv can't really fix a null pointer deref on
this
in C++ code deep within intel-media-driver.
This is already mentioned in the description. 😅
I only opened this a week after opening intel/media-driver#1879 and getting no response.
Can you reproduce the issue with ffmpeg -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format vaapi -i [input] -f null -
? Should help Intel guys isolate the issue. Set the appropriate render device.
There's nothing mpv can do to workaround this, just don't use hwdec.
Can you reproduce the issue with
ffmpeg -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format vaapi -i [input] -f null -
? Should help Intel guys isolate the issue. Set the appropriate render device.
The crash can only be triggered by seeking back and forth multiple times during playback. Not sure how to do that with this.
There's nothing mpv can do to workaround this, just don't use hwdec.
Well, this crash is actually rare enough that I can get away with hwdec almost all the time. 😆
mpv Information
Other Information
Reproduction Steps
I'm re-posting upstream bug intel/media-driver#1879 here for tracking, and just in case it can be worked around in mpv.
After upgrading my CPU from i9-13900K (Raptor Lake S, RPL-S) to Ultra 9 285K (Arrow Lake S, ARL-S), mpv would randomly crash when I click the progress bar to seek in certain (not all) videos. From the backtrace you can see the crash is caused by the Intel media driver.
mpv config:
Expected Behavior
mpv does not crash.
Actual Behavior
Crash in
intel-media-driver
.Log File
Sample Files
No response
I carefully read all instruction and confirm that I did the following:
--log-file=output.txt
.