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: "Bad allocation" error on Windows Vista (Read 3881 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

"Bad allocation" error on Windows Vista

Ever since the betas of .9.5, I've been having a lot of crashes of the "Unhandled exception: bad allocation" variety.  I have no idea what's causing them, and I don't expect anybody else to either.  This is because there are no crash logs being generated, as far as I can tell, by either Foobar or Windows.

How do I proceed from here?  I love .9.5, but I hate having it crash on me every hour or so.  I'm running Vista Ultimate, 32-bit.

"Bad allocation" error on Windows Vista

Reply #1 –
This problem is very likely because you have component(s) that is/are compiled with the old SDK. Please double check and upgrade your components first if necessary. If it still crashes then post your component list please.

"Bad allocation" error on Windows Vista

Reply #2 –
Not that I want to dig up an old post, but this is the most relevant post that I've seen to my issue.

Pretty much what sinfony said, is my situation.

I will, however, list the components I have installed...

Code: [Select]
Core (2008-07-05 15:46:02)
    foobar2000 core 0.9.5.4
foo_abx.dll (2008-05-24 10:23:50)
    ABX Comparator 1.3.3
foo_albumlist.dll (2008-07-05 15:45:20)
    Album List 4.3
foo_audioscrobbler.dll (2008-03-09 14:08:00)
    Audioscrobbler 1.3.16
foo_burninate.dll (2006-08-04 21:56:44)
    Audio CD Writer 2.0.1
foo_cdda.dll (2008-06-25 12:18:24)
    CD Audio Decoder 2.1.3
foo_converter.dll (2008-07-05 15:45:22)
    Converter 1.1.2
foo_dsp_std.dll (2008-06-23 13:41:10)
    Standard DSP Array 1.0
foo_fileops.dll (2008-06-07 14:14:56)
    File Operations 2.1
foo_freedb2.dll (2008-06-07 14:15:10)
    freedb Tagger 0.6
foo_input_std.dll (2008-07-05 15:45:42)
    Standard Input Array 1.0
foo_lock.dll (2007-01-25 13:57:56)
    Pause on Lock 0.4
foo_pqview.dll (2008-03-11 19:02:54)
    Playback Queue Viewer 0.2
foo_removefromqueue.dll (2007-07-14 14:30:00)
    Remove from Queue 1
foo_removeplayed.dll (2007-09-02 13:15:30)
    Remove played Files 1.4.0
foo_rgscan.dll (2008-06-11 13:30:18)
    ReplayGain Scanner 2.0.8    
foo_ui_columns.dll (2007-10-11 18:02:04)
    Columns UI 0.2
foo_ui_std.dll (2008-07-05 15:45:42)
    Default User Interface 0.9.5
foo_unpack.dll (2008-07-05 15:45:22)
    RAR reader 1.1
    ZIP/GZIP reader 1.0
foo_winamp_spam.dll (2008-10-04 18:37:38)
    Winamp API Emulator 0.98


Thanks in advanced.

"Bad allocation" error on Windows Vista

Reply #3 –
look for updates for these components
Code: [Select]
foo_burninate.dll (2006-08-04 21:56:44)
    Audio CD Writer 2.0.1
foo_lock.dll (2007-01-25 13:57:56)
    Pause on Lock 0.4
foo_removefromqueue.dll (2007-07-14 14:30:00)
    Remove from Queue 1
foo_removeplayed.dll (2007-09-02 13:15:30)
    Remove played Files 1.4.0
foo_ui_columns.dll (2007-10-11 18:02:04)
    Columns UI 0.2
Or just remove them from foobar folder.
Who are you and how did you get in here ?
I'm a locksmith, I'm a locksmith.

"Bad allocation" error on Windows Vista

Reply #4 –
/Edit: Solved. Old "foo_uie_quicksearch.dll" was the problem.

"Bad allocation" error on Windows Vista

Reply #5 –
Quote from: A_Man_Eating_Duck on
look for updates for these components
Code: [Select]
foo_burninate.dll (2006-08-04 21:56:44)
    Audio CD Writer 2.0.1
foo_lock.dll (2007-01-25 13:57:56)
    Pause on Lock 0.4
foo_removefromqueue.dll (2007-07-14 14:30:00)
    Remove from Queue 1
foo_removeplayed.dll (2007-09-02 13:15:30)
    Remove played Files 1.4.0
foo_ui_columns.dll (2007-10-11 18:02:04)
    Columns UI 0.2
Or just remove them from foobar folder.

Wow, I just saw this response (and it was based upon a notification of the other response).

I am not 100% sure what I did to fix it but after time I got it all working, haven't had an issue since.

Thanks. :-)