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.

by fridgey at 10:11 AM EDT on June 14, 2011

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.

by manakoAT at 11:11 AM EDT on June 14, 2011

An unhandled win32 exception occured in foobar2000.exe[5120] <- the error comes from the foobar exe itself, not from vgmstream i think

by bcass at 12:19 PM EDT on June 14, 2011

I just removed all the plugins that don't come with foobar as standard and still got the crash when using VGMStream.

by cooljacker at 12:34 PM EDT on June 14, 2011

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.

edited 12:50 PM EDT June 14, 2011

by bcass at 4:38 PM EDT on June 14, 2011

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.

by manakoAT at 11:22 AM EDT on June 15, 2011

upload your foobar dir including the plugins

by bcass at 11:40 AM EDT on June 15, 2011

http://www.megaupload.com/?d=OV3XR4JA

by manakoAT at 10:57 AM EDT on June 17, 2011

Runs fine here, maybe it's something in your system. Broken soundcard maybe?

by hcs at 11:22 AM EDT on June 17, 2011

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.

edited 11:41 AM EDT June 17, 2011

by bcass at 9:59 AM EDT on June 19, 2011

I just tried the latest version with the new dlls but still get the crash. Bizarrely, with VGMStream installed, I get the crash after about 5 mins even if it isn't playing any music. I very much doubt it's a problem with my soundcard as I don't have any audio problems with any other apps.

by hcs at 8:30 PM EDT on June 19, 2011

Very weird, I wonder what could be causing it... what does the plugin even do when it isn't playing music?

by bcass at 8:08 AM EDT on June 20, 2011

I suppose only Josh could answer that one.

When it crashes and I restart foobar, it comes up with an option to refer the error to an online troubleshooter, but when I select this option, the troubleshooter reports that there are "no known problematic components found".

by bcass at 8:16 AM EDT on June 20, 2011

Not sure how useful it is, but here are the report files that Windows (XP SP3) offers to upload after the crash:

http://www.megaupload.com/?d=KDL9BAO5

by kode54 at 2:47 AM EDT on June 21, 2011

There are no crashes logged for the latest foo_input_vgmstream component. You need to submit your crash reports. If the crashes aren't hitting the built-in crash logger, then something strange is going on with the component.

I also have the latest version installed, and as with all previous versions, I cannot reproduce that crash.

by bcass at 7:44 AM EDT on June 21, 2011

When you say submit the crash report, do you mean via the standard Windows method? I've already done this, several times.

by DrO at 3:35 PM EDT on June 21, 2011

he means via the one built into Foobar itself, as i doubt the ones you send via the Windows Reporting Tool makes it way back to Foobar.

-daz

by bcass at 8:35 PM EDT on June 21, 2011

As I already said in a previous post, after a crash and restarting foobar, when I click the "Check online troublshooter" button the resulting webpage simply reports "No known problematic components found".

by kode54 at 10:34 PM EDT on June 21, 2011

That's not the correct crash report submission system. This is the correct dialog:



And if you click the View Report button, it should also open an Explorer window on the crash reports folder, which is located in (foobar2000 configuration folder)\crash reports:

by bcass at 7:42 AM EDT on June 22, 2011

I don't get those screens when it crashes. I only get the Windows Reporting Tool. I checked my "crash reports" folder and the only files in there are from Nov 2010. Here are all the files from the folder:

http://www.megaupload.com/?d=KQIA3DAU

I'm using the latest version of foobar.

I managed to fix it, I hope by Kawaii at 12:28 PM EST on February 18, 2012

It's something to do with it scanning the library, when you have huuuuuuge media libraries, and folders that have a plethora of different files in them, or something like that. If, in your library settings you set it to include only "legit" audio files, like mp3 flac and ape, the library won't try to scan for all the other game files, I've been running it with the library on, with the include only, and it worked just fine for an hour. I hope this helps anyone, I found this thread because I had the same problem, I just new it had to be in the media scanner, the crash dumps say so.

Now I have a problem by Katsur at 9:11 PM EST on December 25, 2023

My Foobar2000 v2.1 Stable version crashes after installing VGMStream component version r1896. It started with my failed attempts at playing TXTP files of Race Driver: GRID music. Now, even trying to play MP3 files, it keeps crashing.

Go to Page 0

Search this thread

Show all threads

Reply to this thread:

User Name		Tags: bold: [b]bold[/b] italics: [i]italics[/i] emphasis: [em]emphasis[/em] underline: [u]underline[/u] small: [small]small[/small] Link: [url=http://www.google.com]Link[/url] [img=https://www.hcs64.com/images/mm1.png]
Password
Subject
Message