VGMStream foobar plugin crash by bcass at 7:27 AM EDT on June 14, 2011
I've been having a regularly recuring crash when using the VGMStream plugin for foobar2000. I have the latest version of the plugin and the latest version of foobar installed.
Foobar crashes after around 5 minutes of playing any filetype (eg MP/FLAC/any of the stream types supported by VGMStream) if I have the VGMStream plugin installed. I have all the relevant support files in the foobar dir. Deleting the VGMStream plugin stops the problem. The error reported is as follows: "An unhandled win32 exception occured in foobar2000.exe[5120]".
Couldn't find a proper site for Josh so have posted this here. I tried older versions of VGMStream but kept getting the same error.
Never had a crash caused by vgmstream in foobar, did you try running foobar with _just_ vgmstream, no other plugins? Could be conflicting with something else you've got going.
Uninstall and reinstall foobar? Also maybe try an older version of foobar? I haven't upgraded it since v1.1.1 and it works great (with the latest vgmstream though).
Also, do you happen to have some music stored in folders that have really, really long file paths? Believe it or not, that can mess up things in foobar.
Already tried all those things. I actually had an older version of foobar installed when it first started happening, then I upgraded to the latest version but still no joy.
It's not a long file path issue as the crashing only happens when I have VGMStream installed. Take VGMStream away and non of the other plugins have any problems.
It may have something to do with file paths, or the particular version of Windows.
Not that these things are at fault, just that they provoke something broken in vgmstream.
edited 11:23 AM EDT June 17, 2011
Actually, when I drop this directory on my winxp box, it doesn't load foo_vgmstream at all. Does it load for you, mana?
edited 11:37 AM EDT June 17, 2011
Oh, this dir doesn't actually have foo_input_vgmstream in it at all. Try picking up the latest version from the component registry, I notice that if nothing else you have a different version of the external dlls.