Comments on: Help me stop the iTunes seziures on Windows XP.

Question: Help me stop the iTunes seziures on Windows XP.

chairface — Wed, 15 Nov 2006 15:59:02 -0800

iTunes 7.X on my Windows box has seizures during the last several seconds of a song. My search fu has failed me.

I have a moderate collection of music (18G) on my iTunes setup on Windows XP. During playback on some (but not all) songs, iTunes will lock up my machine for a few seconds during the last 5 seconds of a song. It's maddening.

I just stumbled across one song that has this seizure problem every five seconds for the entire last minute of the track (which is all silence). I have crossfade playback turned off. The track is not marked as part of a gapless album.

My boss has the exact same problem with his iTunes setup. Any idea how I can make the problem go away?

Apologies in advance for asking yet another iTunes question, and thanks in advance for any advice.

By: null terminated

null terminated — Wed, 15 Nov 2006 16:00:32 -0800

Do you have cross fading on? Is the music on your local hard drive or on some sort of networked disk?

By: chairface

chairface — Wed, 15 Nov 2006 16:12:45 -0800

No. I mention that actually. It was the first thing I tried. The music is on a local USB disk but it was the same problem when it was on the internal disk. USB should have plenty of bandwidth to stream mp3s.

By: null terminated

null terminated — Wed, 15 Nov 2006 16:16:57 -0800

Doh, I should read questions more carefully.

How'bout automatically downloading album artwork? iTunes has notoriously bad internet connection handling.

By: chairface

chairface — Wed, 15 Nov 2006 16:20:31 -0800

I should probably describe these seizures in more detail.

The machine looks like it's locked up. The cursor won't respond. Everything locks up hard, for a few seconds. Then it frees up probably for about 1 second or so. On the long silence song I mentioned, this cycle repeats for the entire one minute of silence.

I've witnessed iTunes lousy album art download. Turing it off was a good suggestion but it didn't help.

By: mphuie

mphuie — Wed, 15 Nov 2006 16:52:58 -0800

Heres a long shot, but have you defragged recently? Are your songs on a removable drive that may have gone to sleep?

By: chairface

chairface — Wed, 15 Nov 2006 17:08:20 -0800

Also good suggestions. The drive is a 30G partition in a 100G external USB drive. That partition only holds music and was recently built by moving my old music onto it so it shouldn't be fragmented much. XP's defrag tool confirms that I don't need to defrag (average fragments per file = 1.01, 16 out of 3,760 files fragmented).

I doubt is has anything to do with the drive going to sleep as it's steaming music the whole time. It is also unlikely that the drive would sleep then wake up repeatedly in a 5 second cycle. And, as I mentioned, the same problem happened when the music was on my internal drive which shouldn't be sleeping much.

It has something to do with the music itself. iTunes is doing something weird during silent bits and/or at the end of tracks. It might be analyzing it for gapless playback or trying to queue up the next track and analyzing that. I'm just not sure.

By: equalpants

equalpants — Wed, 15 Nov 2006 17:15:14 -0800

It might help if you can figure out exactly what iTunes is doing during the lockup--turn on the Performance Monitor (under Control Panel->Administrative Tools, or just run "perfmon"). You can choose things to monitor from a big giant list of stuff (Right-click on the list of counters at the bottom and choose "Add counter"); try a bunch of things and see if any of them jump during the lockup.

A good first batch of things to monitor would be the things that you can see for iTunes specifically. In the "Add Counters" dialog, choose "Process" for the performance object, pick iTunes from the list on the right, and choose "All counters".

Are you using hyperthreading, or multiple cores? If so, a nonresponsive cursor is fairly unusual, but if not, then it's probably just a sign that there's a lot of something going on (CPU usage or paging, probably).

By: chairface

chairface — Wed, 15 Nov 2006 17:47:01 -0800

I have a single core machine, a 2.2G P4.

I added iTunes' counters to perfmon and got the strangest result. The seizures now lasted much longer (around 15 seconds) and perfmon failed to record any data during that time interval. It pops up a dialog about it too. This also happens if I don't have iTunes counters enabled. A quick look at the event log shows nothing of interest either.

I should probably post my System Information too:

OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 2 Build 2600
OS Manufacturer Microsoft Corporation
System Name XXXXX
System Manufacturer Dell Computer Corporation
System Model Precision WorkStation 360
System Type X86-based PC
Processor x86 Family 15 Model 2 Stepping 7 GenuineIntel ~2261 Mhz
BIOS Version/Date Dell Computer Corporation A01, 4/28/2003
SMBIOS Version 2.3
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume2
Locale United States
Hardware Abstraction Layer Version = "5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)"
User Name XXXXX
Time Zone Pacific Standard Time
Total Physical Memory 1,024.00 MB
Available Physical Memory 325.94 MB
Total Virtual Memory 2.00 GB
Available Virtual Memory 1.96 GB
Page File Space 2.41 GB
Page File C:\pagefile.sys

By: chairface

chairface — Wed, 15 Nov 2006 17:50:58 -0800

Ah. I just noticed the task manager's display works during the seizure. It shows a 100% CPU load during the silent part.

By: chairface

chairface — Wed, 15 Nov 2006 17:56:34 -0800

Oookay. I just found some possibly helpful weirdness. If I seek into the silence and start playing, everything is fine. It's only a problem when it transitions from music into silence.

FWIW, Sound Check is disabled. I also tried, as a wild guess, changing my streaming buffer size to large which made no difference either.

By: equalpants

equalpants — Wed, 15 Nov 2006 20:21:15 -0800

Wow, that's pretty weird. Only thing I can think of is to turn off EQ and see if that does anything. It's obviously a terrible bug, of course; I think your only chance is that it might be in something that you can turn off.

(Apparently people have been having trouble with the Windows iTunes for a long long time--that link is from 3 years ago but people are still posting new complaints.)

By: NationalKato

NationalKato — Thu, 16 Nov 2006 08:37:18 -0800

Happens to my Windows box also. Strange and annoying.

By: divabat

divabat — Fri, 17 Nov 2006 03:05:58 -0800

Argh! Same thing happens to me, except it's the very last second. Argh.

By: equalpants

equalpants — Fri, 17 Nov 2006 11:09:36 -0800

By an odd coincidence, Raymond Chen's blog entry for today is about nonresponsive cursors. I wouldn't be surprised if Apple was misusing the low-level mouse hooks he mentions. (Not that that's any help fixing it, unfortunately!)

By: chairface

chairface — Fri, 17 Nov 2006 11:43:39 -0800

I don't know enough about low level windows to know if that's the problem or not. It's clearly related to silent passages so I'm not sure why iTunes would be extra interested in mouse movements at that time. It looks to me like they're tripping a bug in the audio driver/hardware otherwise it's hard to explain why it only happens on some machines.

I doubt they will ever fix it but I did start a thread at Apple's iTunes forum.

By: equalpants

equalpants — Fri, 17 Nov 2006 12:15:47 -0800

Yeah, I guess it's likely to be somehow driver-related; the mouse thing is just a possible explanation for the frozen cursor and the weird perfmon behavior.

The way a mouse hook could screw things up would be if they were doing something in the hook that could potentially take a long time (which you're not supposed to do). For example, if the hook was trying to communicate with some other part of the program--which was screwed up because of some bug with the silence--and getting stuck waiting for it. But of course the actual bug would be somewhere else.

Good luck with the forum; I hope you can get it fixed. (It sounds terribly annoying!)