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: Hangings (Read 2948 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Hangings

A few weeks ago, Foobar started acting weird.  It keeps hanging in the middle of tracks, then resuming a bit later.  While it's hanging, the oscilloscope view displays a growing sine wave pattern.  Sometimes it only hangs for a fraction of a second, sometimes for many seconds.  The longest hang was nearly 30 seconds.  No error messages display while this is happening.  Any help in fixing this issue would be appreciated.

Hangings

Reply #1
Check your Power options. A power saving setting like "Turn off Display" may suspend playback.

Hangings

Reply #2
Please provide more information in accordance with the rules of Support.
Quote
3. Make sure you are using the latest version. [i.e. are you?]

4. Describe your problem exactly.
Write in detail what specifically you were trying to do, what you had expected and what happened instead. [i.e. what has or might have changed “[a] few weeks ago”?]

5. Post other helpful information.
That means usually at least your operating system (Windows) version, a list of all your components […] please use codebox tags around the list so that it doesn't make your post unnecessarily long […], contents of the foobar2000 console […] and any other relevant information, like used music file types for decoding/tagging problems, describe your user interface layout for UI problems, [your output method, settings, and so on,] etc.

Hangings

Reply #3
Sorry about that.

The version I have is the most recent stable version (1.1.13), which I upgraded to from 1.1 on the 9th of August.  These issues started while I was still using 1.1. 

Specifically, what I was trying to do was listen to music, but the player would seize up, display the "expanding wave" in the oscilloscope view, then resume playback sometime after.  While the expanding wave is displayed, the player is entirely unresponsive.  The only things that happened at around the same time was that I installed Rainmeter and Rocketdock to gussy up my desktop, but even after exiting and removing the programs, the issue persists.  It seems more prone to choke on longer songs (Rush's "2112", The Mars Volta's "Cygnus... Vismund Cygnus", Between the Buried and Me's "White Walls", etc.).  It's also very unpredictable, sometimes not giving any problems at all, and other times stalling every 5 seconds.

OS is Windows 7 64-bit, the majority of my music library is in FLAC, and my components are:
Code: [Select]
foo_albumlist
foo_cdda
foo_converter
foo_ui_std
Core
foo_rgscan
foo_dsp_std
foo_input_std

In addition, I also had these ones before I removed them due to the possibility of them being the problem:
foo_gep (Game Emu Player, plays music files ripped from video games)
foo_audioscrobbler (Last.fm connection)


I'm not entirely sure what the last request entails, but I'm listening through headphones using the Primary Sound Driver device, with a buffer length of 2900ms.

As for the power setting issue, the display is set to shut off after 10 minutes, but if my computer is left alone long enough to have the monitors shut off, then I'm not listening to music anyway.

EDIT: I've just updated to 1.1.14b3, and nothing has changed.

Hangings

Reply #4
Thanks; that’s great. No cause is immediately evident to me, but those with better detective skills will certainly benefit from all that info.

Hangings

Reply #5
I had a similar problem caused by too few RAM. The HDD couldn't keep up with foobar and the track lagged when I was loading a game or something.
How much RAM do you have? Is there I/O while the track is hanging?
The very act of observing, influences what happens.

Hangings

Reply #6
I had a similar problem caused by too few RAM. The HDD couldn't keep up with foobar and the track lagged when I was loading a game or something.
How much RAM do you have? Is there I/O while the track is hanging?


I've got 4GB of RAM, which usually doesn't get a load above 60% unless a game is running or I have a lot of tabs open in Chrome.  Even when I close out Chrome completely, and my Phys.Mem. usage drops to 30%, it'll still lag at times.  Having games running at the same time doesn't seem to have too much of an impact on lag, as I can easily have it and TF2 running at the same time.  I don't usually have it running while I'm playing games, though.  For the record, Foobar's currently sitting at ~48 000K of memory usage.  I'm not sure what you mean by input/output while hanging: how would I go about testing that?

 

Hangings

Reply #7
Theres noise from the HDD if theres much I/O, but I guess that isn't your problem anyways.

Your best guess would be to try a clean foobar installation and enable your extensions one by one to see if it either isn't a foobar problem at all or which extension is the culprit.
The very act of observing, influences what happens.

Hangings

Reply #8
I've done a fresh install, but it keeps stalling.  I can't remove any components without causing the player to stop working.

Hangings

Reply #9
I meant remove files from the installation folder's components directory when it's not running.

Hangings

Reply #10
I can remove all of them except foo_input_std and foo_ui_std without it crashing, and it keeps stalling.

Edit: I was thinking there might be some correlation between the seizing and the song's bitrate, but "2112" is 896kbps, and has infrequent stalls, "Cygnus... Vismund Cygnus" is 2986kbps and is entirely unlistenable, but my most recent listen through of "White Walls" at 1006kbps was flawless.

Edit2: Nevermind, White Walls started choking Foobar again.  Maybe it is the bitrates?

Edit3: I don't know if it is the bitrates, because a regular 320 MP3 started choking Foobar now.

Hangings

Reply #11
Hardware HDD problems?

Hangings

Reply #12
See what thread is choking it with Process Explorer and maybe find out where it's stalling from the thread stack trace?

Hangings

Reply #13
Problem solved: my hard drive is damaged and has a bunch of bad sectors.  It's not a problem with foobar at all.  Sorry, folks.  This can be closed up, deleted, whatever.  Thanks for your assistance with this matter, in any case.