Avidemux process hangs on exit with vdpau deint filter

Started by eumagga0x2a, August 22, 2016, 10:30:24 AM

Previous topic - Next topic

eumagga0x2a

STR:


  • Load an interlaced video in Avidemux, select an encoder like e.g. x264 and add the VDPAU deint filter.
  • Save the resulting deinterlaced video, wait until the encoder finishes successfully, acknowledge the notification dialog.
  • Press Ctrl+Q to exit Avidemux.

Actual Results:
The GUI closes, but the avidemux3_qt5 process keeps running consuming 100% of a CPU core until killed. The last words in the terminal:

  [HandleAction]  ************ EXIT **************
  [HandleAction]  Closing ui
Close event!
[HandleAction]  ************ EXIT **************
  [HandleAction]  Closing ui
  [renderDestroy]  Cleaning up Render
  [stop]  stopping simple render.
  [~simpleRender]  Destroying simple render.
[Qvideo]Destroying QVideo
[~myQApplication]  Cleaning render...
  [renderDestroy]  Cleaning up Render
  [~myQApplication]  Cleaning preview...
  [destroy]  Destroying preview
Cleaning up
[destroy]  Destroying preview
  [deleteAll]  [Editor] Deleting all videos
  [vdpGetProcAddressWrapper]  Calling vdpGetProcAddressWrapper for function 38
  [vdpGetProcAddressWrapper]  Wrapping DECODER_DESTROY decoderDestroy
  [vdpGetProcAddressWrapper]  Ok
[lavc] Destroyed
[close]  Destroying TS demuxer
  [~ADM_ptrQueue]  >>>>>>>>Warning queue is not empty
<<<<<<<  [close]  Destroying TS demuxer
  [~ADM_edAudioTrackFromVideo]  Destroying edAudio from video track 0 at 2f5b2c0
  [deleteAll]  [Editor] Deleting all videos
  [cleanup]  Deleting post proc
  [deleteAll]  [Editor] Deleting all videos
[Script] Tinypy INFO - Closing Python
At exit, we have still 5 surface
After cleanup we have  0 surface
[cleanup]  Destroying vdp device..
  [ADM_vf_clearFilters]  clear filters


This is a fallout of [VDPAU] Try to cleanup deeper when something bad happens, that should help preventing out-of-memory errors after a while, verified by reverting the patch.

mean


Jan Gruuthuse

#2
Also take note: vdpau: Resize requires (source) screen sizes in multiples of 16 (x,y). If trying to do with none multiples of 16. Nothing happens.
If this is by design or required (multiples of 16) perhaps a warning window with some explanation?
Would this also apply to target screen sizes?

I have no idea if multiples of 16 applies to any other vdpau stuff?