Known Problematic Components, for foobar2000 0.8.3 Options

[Peter]

Current banlist (as for 0.8.3) (*)

foo_vis_samurize

repeated crash reports

foo_mirc

repeated crash reports

foo_contextsort

repeated crash reports under 0.7.7

foo_dirvol

attempts to override behaviors of standard UI, causing overall instability

Known potential troublemakers

foo_tunes

repeated crash reports, repeated reports of lockup while shutting down, leaving a ghost foobar2000.exe process.

foo_mpg123

private experimental accidentially leaked component not meant for regular use, there are several known problems.

foo_la

has buffer overrun exploits, not closing files after playback, bypassing reader system so unicode filenames, unpackers, streaming, full file buffering, etc don't work.

foo_shuffle

repeated crash reports, crashes often result in loss of configuration file.

foo_winamp_input

broken unicode support, broken multithreading, buffer overrun exploits, several other unfixable issues; use at your own risk.

foo_oddcast

repeated crash reports.

If you are an author of one of above and have fixed the issue, please send me a PM to get this list updated.

(*) Banned components are blocked from being loaded by file name. This action is taken to prevent users from experiencing problems caused by faulty components. If you want to force them to load anyway (or you are a developer and want to test a new version), rename the dll file (e.g. to foo_whatever.dll).