The VideoLAN Forums

I don't remember having this problem before, been using VLC for a while...anyway, here is the story...

When playing movies from any source, VLC will crash at random points - just stop working completely - and freeze in the classic windows "not responding" stage. However, what's not so classic is that it:

a) cannot be shut down at all. Attempts to use task manager to end either the application or the process or the process tree all end in failure. All the right "end task" etc windows pop up, but nothing ever comes of it - the crashed VLC instance just stays there until the computer is hard-rebooted.

and,

b) as soon as VLC crashes, no new programs can load, regardless of program type, dev etc. Any and all programs that are executed after the crash load into memory and can be seen in the taskbar processes list, but do not appear on the screen or in the running applications list. Furthermore, these programs too cannot be end task'ed after they quasi-loaded.

I'm guessing it's nothing to do with drivers/codecs since the problem seems to encompass nearly the entire PC once it happens, but it's bugging the @*#%* out of me, because it basically means that every time I use VLC I risk having to hard-reboot my PC with no alternatives.

Any ideas?

Sorry forgot to give some specs:

VLC 0.8.1 (latest one)
WinXP Pro SP2
Athlon64 3500+
GeforceFX5900XT

These symptoms are completely identical to what I experienced earlier, described here: viewtopic.php?t=853&highlight=

However I seem to get this problem when capturing audio from my TV card, so the circumstances seem to be quite different...

i don't think this thread(or subject) has anything to do with your circumstantial video card support thread. sorry, but i'm not seeing the similarities.

this thread talks about vlc crashing when trying to play video files. your thread talks about crashing in the presence of video cards. while they do both result in vlc crashing, there are two separate explanations and fixes for these two separate problems.

i don't mean a flame at all, just trying to resolve something that i don't understand.
-walloo.

originally posted by maru
===
I found out what's causing the problem during startup!!!!!!!!

The problem isn't the CoreAudio plugin at all but it has something to do with the Coreauido system though. I have FinalCut Pro installed on my system.
It registers a DVCPROHDMuxer.component on the system.
During aout creation this componente gets called and needs a looooong time to init.
Removing the component from the /Library/Quicktime directory gives me instant starting times with VLC.
It is a workaround though, since I need the component for FCPRO

Can someone experiencing the same problem take a look at the /Library/Quicktime, ~Library/Quicktime directories and check if they have other componentes installed which cause this behaviour too?

Mike
===

if there is a better fix, search this whole forum for "DVCPROJDMUXER.COMPONENT' and then help by posting that newer fix all over this forum.

thanks maru.
-walloo.