Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Trying to scan for Replay Gain (foo_rgscan) crashes foobar (Read 643 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Trying to scan for Replay Gain (foo_rgscan) crashes foobar

I started noticing this happening several months ago, and didn't originally think too much of it. Whenever I attempt to do scan tracks for replay gain values. foobar immediately crashes. I thought it was an issue with multichannel files since those are typically the only ones I ever attempt to playback that aren't previously tagged, but discovered today that it's actually all files, FLAC and mp3 included.
I tag all my mp3s on another machine with the same version of x86 foobar which works perfectly fine, but on my primary playback device it always crashes, regardless of file type.

Crash dump shows the following error message:
Code: [Select]
Illegal operation:
Code: E06D7363h, flags: 00000001h, address: 74FD1072h
Additional parameters: 19930520h 00EFF12Ch 00ACD56Ch
Message: Service duplicated

Any ideas on what could be going wrong here? I have no known problematic components. 32-bit foobar now up to date and still seeing the crash. foo_rgscan is 2.0.9 which appears to be the latest.

Re: Trying to scan for Replay Gain (foo_rgscan) crashes foobar

Reply #1 –
Replaygain scanning is built in since 2.0 (not optional). I think foo_rgscan should be removed.

Re: Trying to scan for Replay Gain (foo_rgscan) crashes foobar

Reply #2 –
Quote from: MordredKLB on
I have no known problematic components.

arguable.

foo_discogger has replaced foo_discogs
I have (lots of) firsthand memory and crash issues with enhanced_playback_stats as do others from its discussion thread.
foo_ui_hacks, foo_jesus, foo_spider_monkey_panel are all questionable at best.

Re: Trying to scan for Replay Gain (foo_rgscan) crashes foobar

Reply #3 –
Quote from: marc2k3 on
Replaygain scanning is built in since 2.0 (not optional). I think foo_rgscan should be removed.
That was it! Thanks.

Re: Trying to scan for Replay Gain (foo_rgscan) crashes foobar

Reply #4 –
Quote from: mjm716 on
Quote from: MordredKLB on
I have no known problematic components.

arguable.

foo_discogger has replaced foo_discogs
I have (lots of) firsthand memory and crash issues with enhanced_playback_stats as do others from its discussion thread.
foo_ui_hacks, foo_jesus, foo_spider_monkey_panel are all questionable at best.
Well the online checker doesn't report anything as problematic.

foo_jesus still works great, although arguably probably not needed anymore. ui_hacks is only installed for testing theme stuff and is not actually doing anything. SMP can probably get you in trouble if you don't know what you're doing.
Also I'm the author of enhanced_playback_stats so I'll try not to take affront at you calling that questionable. :D Make sure you see my response to you about your crash. If you can get simple repro steps I'm happy to get it fixed.

Re: Trying to scan for Replay Gain (foo_rgscan) crashes foobar

Reply #5 –
Out of curiosity, do you bypass the installer and instead extract and handle file replacements manually? The installer is meant to take care of cleanups like this.

Btw, you should be safe with removing foo_ac3, foo_input_dts and foo_out_wasapi. Their functionalities are built-in.

Re: Trying to scan for Replay Gain (foo_rgscan) crashes foobar

Reply #6 –
Quote from: Case on
Out of curiosity, do you bypass the installer and instead extract and handle file replacements manually? The installer is meant to take care of cleanups like this.

Btw, you should be safe with removing foo_ac3, foo_input_dts and foo_out_wasapi. Their functionalities are built-in.
Honestly, I'm not sure anymore. I know the first time I installed a version of 2.0 I had some upgrade stuff that didn't work completely right (can't remember exactly what) and so I went back to 1.6x or whatever for a while until I heard the 2.0 upgrade stuff was sorted out.

I'm almost positive I would have ended up nuking that original 2.0 installation though and starting over. My guess is that I probably did something dumb like copy my existing components folder over into 2.0 after installation since I'm still using x86 for SMP. support and I was unaware that much of that functionality got built in. Thanks for the tip and I'll remove those other extraneous components.