Opened 2 years ago
Last modified 2 years ago
#8654 new defect
Crash with kmsgrab, scale_vaapi and hwdownload
| Reported by: | 0x53ee71ebe11e | Owned by: | |
|---|---|---|---|
| Priority: | important | Component: | undetermined |
| Version: | git-master | Keywords: | vaapi crash |
| Cc: | Blocked By: | ||
| Blocking: | Reproduced by developer: | no | |
| Analyzed by developer: | no |
Description
While trying to figure out another problem (#8377, may or may not be related), I came upon this crash:
ffmpeg_g -v 9 -loglevel 99 -f kmsgrab -framerate 60 -i - -map 0 -vf 'hwmap=derive_device=vaapi,scale_vaapi=960:540,hwdownload,format=bgr0' -c:v h264 -preset veryfast /tmp/output.mp4
I changed the command line from over in that other ticket. The idea was to skip the hardware encoder and use the software encoder instead after scaling down the source on the gpu. And I was greeted with a crash. See attachement.
Leaving out the scale_vaapi filter works without crash.
I am not sure if using scale_vaapi without using the vaapi encoder afterwards is even a valid thing to do, but it shouldn't crash no matter what.
Attachments (1)
Change History (3)
by , 2 years ago
| Attachment: | output.txt added |
|---|
comment:1 by , 2 years ago
| Component: | ffmpeg → undetermined |
|---|---|
| Summary: | Crash with kmsgrab, vaapi_scale and hwdownload → Crash with kmsgrab, scale_vaapi and hwdownload |
comment:2 by , 2 years ago
| Keywords: | vaapi crash added |
|---|---|
| Priority: | normal → important |
Note:
See TracTickets
for help on using tickets.
Looks like "wrong bug tracker" to me.