vlc in C# application crashed for libffmpeg_plugin.dll

[swatforce]

An C# application embeds vlc in client server to play the media stream from the streaming server, which generated also by vlc:
vlc –vvv samplevideo_800kbps.mov ––sout “#transcode{acodec=mp3,ab=192,channels=2}:duplicate{dst=std{access=udp,mux=ts,dst=16.157.129.39:1234}}” –L

After playing several minutes, the C# application crashed with an Windows2003 error messagebox. In the system log, I find the error:
.NET Runtime 2.0 Error Reporting
Faulting application multiviewer.exe, version 1.0.0.0, stamp 4857aaea, faulting module libffmpeg_plugin.dll, version 0.0.0.0, stamp 459cec9f, debug? 0, fault address 0x001257c7.

The faulting module could also be liblibmpeg2_plugin.dll or unknown.
The vlc version is 0.8.6e.

Is there anybody can help me with this?

[swatforce]

The detailed error info:

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 1000
Date: 2008-07-02
Time: 15:15:17
User: N/A
Computer: aaaaa
Description:
Faulting application multiviewer.exe, version 1.0.0.0, stamp 4857aaea, faulting module libffmpeg_plugin.dll, version 0.0.0.0, stamp 459cec9f, debug? 0, fault address 0x001257c7.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 00 70 00 70 00 6c 00 A.p.p.l.
0008: 69 00 63 00 61 00 74 00 i.c.a.t.
0010: 69 00 6f 00 6e 00 20 00 i.o.n. .
0018: 46 00 61 00 69 00 6c 00 F.a.i.l.
0020: 75 00 72 00 65 00 20 00 u.r.e. .
0028: 20 00 6d 00 75 00 6c 00 .m.u.l.
0030: 74 00 69 00 76 00 69 00 t.i.v.i.
0038: 65 00 77 00 65 00 72 00 e.w.e.r.
0040: 2e 00 65 00 78 00 65 00 ..e.x.e.
0048: 20 00 31 00 2e 00 30 00 .1...0.
0050: 2e 00 30 00 2e 00 30 00 ..0...0.
0058: 20 00 34 00 38 00 35 00 .4.8.5.
0060: 37 00 61 00 61 00 65 00 7.a.a.e.
0068: 61 00 20 00 69 00 6e 00 a. .i.n.
0070: 20 00 6c 00 69 00 62 00 .l.i.b.
0078: 66 00 66 00 6d 00 70 00 f.f.m.p.
0080: 65 00 67 00 5f 00 70 00 e.g._.p.
0088: 6c 00 75 00 67 00 69 00 l.u.g.i.
0090: 6e 00 2e 00 64 00 6c 00 n...d.l.
0098: 6c 00 20 00 30 00 2e 00 l. .0...
00a0: 30 00 2e 00 30 00 2e 00 0...0...
00a8: 30 00 20 00 34 00 35 00 0. .4.5.
00b0: 39 00 63 00 65 00 63 00 9.c.e.c.
00b8: 39 00 66 00 20 00 66 00 9.f. .f.
00c0: 44 00 65 00 62 00 75 00 D.e.b.u.
00c8: 67 00 20 00 30 00 20 00 g. .0. .
00d0: 61 00 74 00 20 00 6f 00 a.t. .o.
00d8: 66 00 66 00 73 00 65 00 f.f.s.e.
00e0: 74 00 20 00 30 00 30 00 t. .0.0.
00e8: 31 00 32 00 35 00 37 00 1.2.5.7.
00f0: 63 00 37 00 0d 00 0a 00 c.7.....

[VLC_help]

Those basic WIndows crash messages are usually useless. If you can do backtraces, that would help. Other option might be nightly builds if they support what you need.
http://nightlies.videolan.org/

[swatforce]

It's hard to track. The issue happens randomly. Sometimes in several minutes, or in one hour.
I find a bug report about libffmpeg_plugin.dll in http://trac.videolan.org/vlc/ticket/1012. Is this related to my issue?

[VLC_help]

ffmpeg combines about all video and audio decoding modules so there are prolly several bugs in it. That is also why it is very important that someone can duplicate the problem.

[swatforce]

I embed vlc into the C# winform application via VLanControl. The libffmpeg_plugin error occurs always in long time playing. So at first I want to locate which module results in the error. The C# application or vlc itself? Does the windows error message mean it's a bug of libffmpeg_plugin.dll?

Besides, if I start vlc player instead of the C# application to receive video streaming, the error almost never happens.

thx!

[VLC_help]

Usually the crash report dll is the correct one (or at least some other module causes that libffmpeg_plugin.dll to crash).

[swatforce]

That's a so strange issue. I tested 0.8.6a to 0.8.6h, and the C# application always crashed by libffmpeg_plugin.dll, but vlc player of the corresponding version never crashed.
Anyway, thx!

[swatforce]

Usually the crash report dll is the correct one (or at least some other module causes that libffmpeg_plugin.dll to crash).

Now I've got the log of VLC, maybe it's helpful.
There are so many msg such as "ffmpeg warning: warning: first frame is no keyframe" and "ffmpeg warning: Bits overconsumption: 58651 > 58576 at 11x18" in the log, and then Windows2003 reports a .Net Runtime 2.0 error and terminates my application, with the message "libffmpeg_plugin.dll error".

The whole log file is in http://www.esnips.com/doc/498dbe6b-94c3 ... log-of-vlc
Plz help to check it! thx in advance!

[swatforce]

How to understand the log information?

[swatforce]

Keep asking....

The log of VLC is in http://www.esnips.com/doc/498dbe6b-94c3 ... log-of-vlc

Take a look at this strange issue...

[VLC_help]

Log doesn't tell directly why VLC crashes. But ffmpeg codec (Windows Media Video 3) make me think the reason is WMV3 decoder. And I would suggest NOT to put WMV video inside TS container if you want to play it with VLC.

[swatforce]

Log doesn't tell directly why VLC crashes. But ffmpeg codec (Windows Media Video 3) make me think the reason is WMV3 decoder. And I would suggest NOT to put WMV video inside TS container if you want to play it with VLC.

Thx!
It seems WMV is more easily to encounter this issue than the other formats such as .MOV and .MPG. I'll try the other videos. Thank you very much!

[swatforce]

Log doesn't tell directly why VLC crashes. But ffmpeg codec (Windows Media Video 3) make me think the reason is WMV3 decoder. And I would suggest NOT to put WMV video inside TS container if you want to play it with VLC.

I tested the other formats such as .MOV and .MPG files, the issue is still there.
And more VLC instances my C# application has, more easily the issue happens.
The fault module could be libffmpeg_plugin.dll or liblibmpeg2_plugin.dll.
Because I'm using VLanControl as the binding dll, I could only use VLC of version0.8.6 to 0.8.6i, but the test results are always the same.

[VLC_help]

My only suggestion is that you change to nightlies. And if the problems still continue, do backtraces and provide us info about backtraces.

[swatforce]

Yes, I've noticed that you've mentioned the night builds. But my application is based on the C# binding dll VLanControl project, and this dll is based on 0.8.6. The night builds version is 0.9.0 now. They are not compliant.

And about backtrace, I'm wondering how to backtrace the error. The error doesn't happen in my C# application, so I can't trace it in debug environment. I think the only thing I can do is getting the VLC log. Any other backtrace solution, please inform me. Thx in advance!!

[VLC_help]

http://wiki.videolan.org/Win32CompileCy ... ebugger.29
Cygwin backtrace is AFAIK only working method for Windows to do VLC backtraces. 0.8.6 will become dead branch as soon as 0.9.0 hits stable and that is why I recommend 0.9.0

[emr_iii]

I too have struggled with this exact same VLC libffmpeg_plugin.dll glitch. Were you ever able to use the GNU debugger to find a resolution?
I have converted all of my project code to the new 0.9.8.1 and the issue is still occurring.
The nasty thing about this VLC bug is that there is no way to catch it even with c# global error handling
void Application_ThreadException(object sender, System.Threading.ThreadExceptionEventArgs e)
void CurrentDomain_UnhandledException(object sender, UnhandledExceptionEventArgs e)

How might someone go about modifying the error handling inside the libffmpeg_plugin.dll in order to log and continue ?

Thank you and have a Prosperous New Year.

[VLC_help]

Without debug information it is impossible to know what part of libffmpeg_plugin.dll cause the issue and fix the bug. AFAIK the libffmpeg_plugin.dll doesn't have any real exception system and I am sure there would be some problems if you try to catch mingw code exception in Microsoft compiled program.