Forum

Filestream (EX9.Texture VLC) / Filestream (DX11.Texture VLC) crash vvvv in erratic manner

When loading more than one video with Filestream (EX9.Texture VLC) vvvv sometimes crashes. Unfortunately the issue occurs in an erratic manner, it might work 10 times in a row but then suddenly crashes.

When it crashes the following dialog pops up (as many times as the number of videos loaded):

TTY doesn’t ouput anything special.

VVVV keeps running but the texture output is no longer updated for all videos and the textures might look distorted/glitchy. As soon as the OK button in the dialog window is clicked vvvv stops working.
https://vvvv.org/sites/default/files/imagecache/large/images/ProgrammSchliessen.PNG

Problemsignatur:
  Problemereignisname:	APPCRASH
  Anwendungsname:	vvvv.exe
  Anwendungsversion:	4.5.30.0
  Anwendungszeitstempel:	519d35f6
  Fehlermodulname:	libavcodec_plugin.dll
  Fehlermodulversion:	0.0.0.0
  Fehlermodulzeitstempel:	516ae05b
  Ausnahmecode:	40000015
  Ausnahmeoffset:	000d737a
  Betriebsystemversion:	6.1.7601.2.1.0.256.1
  Gebietsschema-ID:	1031
  Zusatzinformation 1:	9057
  Zusatzinformation 2:	9057e36ad2ed17031a4bcebc75883293
  Zusatzinformation 3:	b04e
  Zusatzinformation 4:	b04ed3d6bfebe718b1b2378229e8a99d

When “Programm Schliessen” (Close Program) is clicked a vvvv exception dialog pops up but it’s impossible to view the details because instantly after that vvvv is force closed.

The windows event log contains the following error message(s):

Name der fehlerhaften Anwendung: vvvv.exe, Version: 4.5.30.0, Zeitstempel: 0x519d35f6
Name des fehlerhaften Moduls: libavcodec_plugin.dll, Version: 0.0.0.0, Zeitstempel: 0x516ae05b
Ausnahmecode: 0x40000015
Fehleroffset: 0x000d737a
ID des fehlerhaften Prozesses: 0x11c8
Startzeit der fehlerhaften Anwendung: 0x01ce5b7aac803318
Pfad der fehlerhaften Anwendung: D:\VLC-Debug\vvvv\vvvv_45beta30_x86\vvvv.exe
Pfad des fehlerhaften Moduls: C:\Program Files (x86)\VideoLAN\VLC\plugins\codec\libavcodec_plugin.dll





Name der fehlerhaften Anwendung: vvvv.exe, Version: 4.5.30.0, Zeitstempel: 0x519d35f6
Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 6.1.7601.17965, Zeitstempel: 0x506dbe50
Ausnahmecode: 0xc0020001
Fehleroffset: 0x0000c41f
ID des fehlerhaften Prozesses: 0x1250
Startzeit der fehlerhaften Anwendung: 0x01ce5b7a3f3acc3f
Pfad der fehlerhaften Anwendung: D:\VLC-Debug\vvvv\vvvv_45beta30_x86\vvvv.exe
Pfad des fehlerhaften Moduls: C:\Windows\syswow64\KERNELBASE.dll

The problem seems to occur more often when the number of videos is increased (I used up to 18) and the videos are loaded directly after vvvv start up (maybe some kind of timing issue??).

The problem seems to be independent of the used container / codecs.
Tested with:

  • WMV - WMV 9

  • MP4 - h264

  • AVI - h264

  • AVI - MJPEG (Picvid)

  • AVI - XVID

  • 25 FPS

  • different sizes.

The Videos were encoded using Adobe Media Encoder or Virtual Dub.

Used 45beta30_x86 and 45beta29.2_x86.

Tested on different machines:

  • Win 7 Pro 64-bit
  • NVidia GTX 580 / Ati-Amd Radeon HD 7900 (with latest drivers)

Forgot to mention that I also tried different VLC versions, 2.0.0 - 2.0.6 , all of them show the same behaviour - versions below 2.x don’t work at all.

Just tried with Filestream (DX11.Texture VLC) from @vux 's
latest DX11 pack (vvvv-packs-dx11-b30-x86) and it shows the same behaviour.

11 quite solid here

well try to tell this to a client while standing in front of a crashed vvvv installation that’s supposed to be running on a big ass video-wall :)

yea, was quite worse at times, but 18-n videos, mmmmm
don’t get me wrong, you know there is a leaks in vlc node?
i’m using up to 6 vids maximum and it also crashes at times…
but i’m not sure if there is cure for that…

different system new error messages

Application: vvvv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
   at Microsoft.Win32.Win32Native.CoTaskMemFree(IntPtr)
   at LibVlcWrapper.LibVlcMethods.libvlc_errmsg()
   at VVVV.Nodes.Vlc.FileStreamVlcNode+MediaRenderer.UpdateMediaPlayerStatus()
   at VVVV.Nodes.Vlc.FileStreamVlcNode+MediaRenderer.UpdateMediaPlayerStatus_Threaded(System.Object)
   at VVVV.Nodes.Vlc.FileStreamVlcNode+MediaRenderer.EvaluateThreadProc()
   at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart()

and

Name der fehlerhaften Anwendung: vvvv.exe, Version: 4.5.29.2, Zeitstempel: 0x5116ef36
Name des fehlerhaften Moduls: ntdll.dll, Version: 6.1.7601.17725, Zeitstempel: 0x4ec49b8f
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0002e41b
ID des fehlerhaften Prozesses: 0x1074
Startzeit der fehlerhaften Anwendung: 0x01ce5c5eaa0532c4
Pfad der fehlerhaften Anwendung: C:\Users\user\Desktop\dmg-energysolutions\vvvv\vvvv_45beta29.2_x86\vvvv.exe
Pfad des fehlerhaften Moduls: C:\Windows\SysWOW64\ntdll.dll
Berichtskennung: 6a5d1dfc-c852-11e2-9be4-f46d0499ccfc

had a look at vvvv with process explorer during a crash:

OriginalSize (439.2 kB)

smells like threading issues… as the different instances of vlc don’t know of each other they can’t guarantee thread safety. but that’s just a guess.