AppName: vlc.exe AppVer: 0.8.6.0 ModName: libwxwidgets_plugin.dll
ModVer: 0.0.0.0 Offset: 00171183
This random pain has been afflicting my past two computers, as well. It's not a crippling problem, but it's been affecting me for a really long time. (further back than I can remember - years)
I'm currently using 0.8.6d now, and the problem happens with any format, whether it's audio and video, or either by themself.
I've done the suggestions from this thread (I tried disabled preparsing, float32 output, overlay...), and others suggestions from way back when it originally started happening. (up until this month I believed it was something wrong with my hardware)
Though, honestly I've never used VLC from the command line, so I there are still some stones unturned.
The system I have now is an AMD Athlon 64 X2, running WinXP SP1 with the codec pack CCCP and FFDShow alpha 2004 Oct 12. The previous system had a 3GHz Pentium 4, with pretty much the same software but I also tried SP2 on it. The only hardware these systems have in common now is the power supply, case and a SATA harddrive - the pagefile is not on that SATA drive, nor is the OS or audio/video being played, and the power supply is an Ultra ULT-600P (600Watt). I'll probably switch cases in the next couple months, to see if somehow it's a noise issue or bad grounding.
What both systems have had in common is Realtek AC'97 audio and an Nvidia graphics card chipset. I've tried a SoundBlaster 16 & Audigy on the previous system, to no effect. These aren't the same devices in the new system, just the same brands. Currently installed drivers for the AC'97 are by Realtek Semiconductor Corp. with the version 5.10.0.6160 from 8/18/2006.
I added -vvvv to VLC, launched it and played an mp3 repeatedly until it crashed. Occasionally when it crashed, I was still able to interact with the messages dialog. (when it didn't just crash/quit, without showing any message)
This is the final part of the messages dialog:
Code: Select all
...
main debug: thread times: real 0m0.609375s, kernel 0m0.000000s, user 0m0.000000s
main debug: thread 4256 joined (directx.c:598)
main debug: removing module "aout_directx"
main debug: removing module "float32tos16"
main debug: removing module "float32_mixer"
main debug: thread times: real 0m0.656250s, kernel 0m0.015625s, user 0m0.000000s
main debug: thread 3972 joined (input/input.c:412)
main debug: creating new input thread
main debug: waiting for thread completion
main debug: thread 3972 (input) created at priority 1 (input/input.c:265)
main debug: drive letter D: found in source
main debug: `D:\Ladytron - 3 Albums\Ladytron - Witching Hour\Ladytron - 07 - Witching Hour - Sugar.mp3' gives access `' demux `' path `D:\Ladytron - 3 Albums\Ladytron - Witching Hour\Ladytron - 07 - Witching Hour - Sugar.mp3'
main debug: creating demux: access='' demux='' path='D:\Ladytron - 3 Albums\Ladytron - Witching Hour\Ladytron - 07 - Witching Hour - Sugar.mp3'
main debug: looking for access_demux module: 1 candidate
main debug: creating access '' path='D:\Ladytron - 3 Albums\Ladytron - Witching Hour\Ladytron - 07 - Witching Hour - Sugar.mp3'
main debug: looking for access2 module: 5 candidates
vcd debug: trying .cue file: D:\Ladytron - 3 Albums\Ladytron - Witching Hour\Ladytron - 07 - Witching Hour - Sugar.cue
vcd debug: could not find .cue file
access_file debug: opening file `D:\Ladytron - 3 Albums\Ladytron - Witching Hour\Ladytron - 07 - Witching Hour - Sugar.mp3'
main debug: using access2 module "access_file"
main debug: pre-buffering...
main debug: received first data for our buffer
main debug: pre-buffering done 1408981 bytes in 0s - 91724 kbytes/s
main debug: creating demux: access='' demux='' path='D:\Ladytron - 3 Albums\Ladytron - Witching Hour\Ladytron - 07 - Witching Hour - Sugar.mp3'
main debug: ID3v2.3 revision 0 tag found, skipping 40960 bytes
main debug: looking for demux2 module: 45 candidates
main debug: looking for packetizer module: 17 candidates
main debug: using packetizer module "mpeg_audio"
mpga debug: xing vbr value present (78)
mpga debug: xing frames&bytes value present (5520760 bytes, 6541 frames, 1152 samples/frame)
mpeg_audio debug: MPGA channels:2 samplerate:44100 bitrate:128
main debug: selecting program id=0
main debug: looking for id3 module: 1 candidate
id3tag debug: checking for ID3 tag
id3tag debug: found ID3v1 tag
id3tag debug: found ID3v2 tag
main debug: using id3 module "id3tag"
main debug: removing module "id3tag"
main debug: using demux2 module "mpga"
main debug: looking for a subtitle file in D:\Ladytron - 3 Albums\Ladytron - Witching Hour\
The next lines that would appear (if it hadn't crashed)
Code: Select all
main debug: looking for decoder module: 28 candidates
main debug: using decoder module "mpeg_audio"
main debug: thread 4020 (decoder) created at priority 2 (input/decoder.c:159)
main debug: meta information:
...(I left out the remainder)
The line "looking for a subtitle..." was consistently the last thing reported before the crash dialog appeared and the GUI became unresponsive.
Printing the debug messages before or after that process begins might mean it's something to do with the decoder modules though.
I'd swear this problem was also noticable in other players, where winamp would also crash and WMP "stuttered" at random times (but didn't crash). However, that was something I haven't tested on this new system - and it may have been RAM related back then... I'll check that out soon, but then that'd kinda excuse VLC and pass the buck to MS ...and ultimately it'd be resolved by the same place the crate ended up in raiders of the lost arc.
Other programs don't crash randomly, and I've seen firsthand what bad motherboard capacitors, faulty/overclocked ram and a lot of other hardware problems do - and this problem has been very specific and reproducible.
On top of everything, I'm also a lazy programmer, but I mean >very< lazy. So I'd have to snap before I'd try digging through source and recompiling with changes. Computer AV isn't my area of expertise, I'm an embedded systems developer with C, ASM and VHDL. (I could build a talking clock or ... I don't know, a sighing clock)
If nobody has any thoughts, I might do more than just report the issue. But it'd be a miracle if I could find a software cause, myself.