Re: [xine-devel] Assertion failure (Rc0a) Video_out.c:137

[Jeroen A. <j.a...@it...>]

Miguel Freitas wrote:

>Hi,
>
>On Mon, 2003-09-08 at 04:21, Jeroen Asselman wrote:
>  
>
>>I got this assertion failure with xine:
>>video_out.c:137: vo_append_to_img_buf_queue_int: Assertion 'img->next == 
>>((void *)0)' failed.
>>    
>>
>
>this is usually caused by buggy decoder drawing (or freeing) the same
>frame more than once... did you changed something at libmpeg2?
>  
>
No, nothing, only the v4l plugin was modified. (See the patch I send 
earlier, rejected?).

>>Unfortunately I can't create a backtrace as xine is running on a 
>>read-only image. The problem occured after 38 hours running xine 
>>continuesly playing the same stream. There were a couple of "libmpeg2: 
>>stream not demultiplexed ?" warnings, I can't tell if those 2 are related.
>>    
>>
>
>actually a backtrace would be very interesting...
>  
>
I am trying to get one, but I am afraid I won't succeed here. Xine is 
launched with the xine-plugin in mozilla and that is where the assertion 
happened. I guess no core will be dumped in this case. I am not sure if 
we can reproduce the error with xine-ui yet. I hope rc0a doesn't have 
the asserts disabled to dump core?

>>Another note: I tested it with 2 setups. They both stopped playing at 
>>the same time. The assertion failure is the same for both, and they both 
>>froze at exactly the same image, even though they weren't started at the 
>>same time.
>>
>>    
>>
>
>by any chance, do you have a copy of the stream at this point? maybe it
>would be possible to reproduce the bug without playing for 38 hours.
>  
>
No I don't (yet). We'll be trying to get a part of the stream, but we 
need to make some adjustments in our code first. I can't make any 
promises though.

-- Jeroen

  ITsec Professional Services, Postbus 5120, 2000 GC  HAARLEM
  Tel: +31 - (0)23 542 05 78       Fax: +31 - (0)23 534 54 77