From: SourceForge.net <no...@so...> - 2005-10-10 08:55:17
|
Bugs item #1319154, was opened at 2005-10-09 02:00 Message generated for change (Settings changed) made by tmattern You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109655&aid=1319154&group_id=9655 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: xine Group: current cvs version Status: Open Resolution: None Priority: 5 Submitted By: Dave Baker (dbkr) >Assigned to: Thibaut Mattern (tmattern) Summary: xine-lib libffmpeg Direct Rendering img freeing Initial Comment: When ENABLE_DIRECT_RENDERING is defined in src/libffmpeg/video_decoder.c, xine-lib will lose frame buffers ('img's) at a rate of one for each stream that is played. Something in the direct rendering code is causing a frame obtained through vo_get_frame (usually called as this->stream->video_out->get_frame, 'this' being an ff_video_decoder_t) not being placed back onto the free queue. This will eventually cause a deadlock where the video-out thread waits indefinately for a decoded frame whilst the decoder also waits indefinately for a blank frame to decode to, and this continues forever since there are no frames left. Symptoms: Xine will stop responding some time into a long playlist of files that are decoded using the ffmpeg plugin. Steps to reproduce: Find a file that xine uses ffmpeg to read (eg. DV). Create a long playlist looping this file for at least 15 times. Play the playlist. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109655&aid=1319154&group_id=9655 |