Aces High Bulletin Board

Help and Support Forums => Technical Support => Topic started by: Mace2004 on December 07, 2008, 04:07:20 PM

Title: iTunes issues
Post by: Mace2004 on December 07, 2008, 04:07:20 PM
I've seen a couple of other folks mention this problem but since installing iTunes I've been getting increased warping and, occasionally, iTunes will pop-up an update screen in the middle of the game.  This is in spite of the fact that I use Alacrity and have all the processes reduced to less than 20 including shutting down all obvious iTunes and 'updater' related ones.  I've looked up all the remaining processes and none are apparently used by iTunes but this updater is still running in the background.  Also, I've disabled automatic update in iTunes.  Uninstalling iTunes is not really an option since I need it for my 3g so has anyone else tracked this bugger down?
Title: Re: iTunes issues
Post by: Tigger29 on December 09, 2008, 07:31:11 PM
iTunes adds at least 5 new processes... let's look at mine here:

issch.exe
iTunesHelper.exe
iPodService.exe
mDNSResponder.exe
AppleMobileDeviceService.exe

These five weren't present before my wife installed iTunes.

I've heard iTunes is a pain to get completely off of a system, but the GOOD news is that it seems that manually closing these processes seems to do well enough, at least on my system.

Eventually I'm going to get around to making another hardware profile, and disabling all of these extra things in that... but I keep putting it off...

Another option is to use a different software... I set up a program called "floola" on a friend's computer, as he was running Win2K and the older version of iTunes that was required because of the older OS wasn't compatible with his new Nano... worked like a charm.

Media Monkey looks good too, but doesn't convert unless you pay for it...
Title: Re: iTunes issues
Post by: Mace2004 on December 09, 2008, 08:31:32 PM
Thanks Tigger.  I found three of those and have them shut down but the other two have no obvious connection. I'll take care of them when I get home this weekend and see if that works. Thanks again.
Title: Re: iTunes issues
Post by: Skuzzy on December 10, 2008, 05:21:51 AM
iTunes does horrible things to your network connection.  Matter of fact, every network related application Apple makes to run on the PC does bad things to the PC.
Title: Re: iTunes issues
Post by: moot on December 10, 2008, 06:15:04 AM
Skuzzy is it enough to kill those processes in Tigger's post?
Title: Re: iTunes issues
Post by: Skuzzy on December 10, 2008, 06:28:58 AM
Not sure moot.  I'll have to put together a junker system to test it with as there is no way I will install an Apple program on any of my PC's.  They remind me of Roxio software, where they assume full control of your PC and also assume you will only be using it for thier application.
Title: Re: iTunes issues
Post by: RTHolmes on December 10, 2008, 07:43:52 AM
use FSAutoStart and set it up to kill any unecessary processes before you start AH. There's loads of stuff in windoze that will effect your network/cpu usage which isnt needed for AH. Singling out Apple seems a bit unfair - pretty much any modern software out there for PCs infests your system with processes which can cause problems.
Title: Re: iTunes issues
Post by: Skuzzy on December 10, 2008, 08:10:12 AM
No, some are far worse than others.  Apple's stuff will interfere with other networking applications.  Not many other applications are as heinous as iTunes, as it pertains to network operations.
Title: Re: iTunes issues
Post by: Mace2004 on December 10, 2008, 09:06:23 AM
use FSAutoStart and set it up to kill any unecessary processes before you start AH. There's loads of stuff in windoze that will effect your network/cpu usage which isnt needed for AH. Singling out Apple seems a bit unfair - pretty much any modern software out there for PCs infests your system with processes which can cause problems.
As I mentioned in my op I use Alacrity which is a more advanced version of FSAutostart and have my running prcessess down to 21. When I still have a window popup in the middle of AH that announces a new update to iTunes you can be pretty sure Apple is behind it. Hopefully with the two additional processes Tigger mentioned I can drive a stake through Apple's core!
Title: Re: iTunes issues
Post by: RTHolmes on December 10, 2008, 09:46:04 AM
sure if the iTunes updates popping up then theres more to kill. sry didnt read the OP properly, had a look at alacrity and instantly put off by the .Net requirement (seems odd to use .Net when you're trying to reduce processes/cpu load :confused:)

skuzzy do you know what networking apps it effects and how? u got me worried now :uhoh
Title: Re: iTunes issues
Post by: Skuzzy on December 10, 2008, 11:08:54 AM
iTunes merrily polls away at the remote server.  What all it is doing is beyond me.  I have not built a trash system to test it.

I know several individuals who have gotten much better performance within Aces High II once they removed iTunes.  Even removed it seems to leave some residuals around.  This is what bugs me.

Like Roxio software.  Once you install it, it owns you until you reformat the hard drive.

I'd like to see the results of a "netstat -an", when iTunes is installed and running.
Title: Re: iTunes issues
Post by: Getback on December 10, 2008, 12:30:41 PM
I have itunes but not on my game machine.  :rock
Title: Re: iTunes issues
Post by: RTHolmes on December 10, 2008, 12:46:07 PM
ah thats probably the broadcast service discovery thing like NetBIOS (Apple call it Rendezvous.) Turning off iTunes sharing in the prefs should stop it, although I killemall with FSAuto anyway so not an issue.

I know what you mean about roxio, I'll add Norton too. Actually its a pretty long list ...  :rolleyes:

I haven't really found anything which loiters after running FSAuto, my PC has every piece of software/service that we use on all the pcs at work - and thats alot (much of it badly written and implemented) - as well as a couple of games. Dont really think theres a need for dual boot/VMs for a gaming machine, just keep FSAuto up to date :)
Title: Re: iTunes issues
Post by: RTHolmes on December 10, 2008, 12:53:56 PM
FYI heres another box running iTunes before FSAuto:

>netstat -an

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3689           0.0.0.0:0              LISTENING
  TCP    127.0.0.1:1027         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:1028         127.0.0.1:27015        ESTABLISHED
  TCP    127.0.0.1:1032         127.0.0.1:1033         ESTABLISHED
  TCP    127.0.0.1:1033         127.0.0.1:1032         ESTABLISHED
  TCP    127.0.0.1:1034         127.0.0.1:1035         ESTABLISHED
  TCP    127.0.0.1:1035         127.0.0.1:1034         ESTABLISHED
  TCP    127.0.0.1:1127         127.0.0.1:27015        ESTABLISHED
  TCP    127.0.0.1:1128         127.0.0.1:5354         ESTABLISHED
  TCP    127.0.0.1:1129         127.0.0.1:5354         ESTABLISHED
  TCP    127.0.0.1:1130         127.0.0.1:5354         ESTABLISHED
  TCP    127.0.0.1:1131         127.0.0.1:5354         ESTABLISHED
  TCP    127.0.0.1:1132         127.0.0.1:5354         ESTABLISHED
  TCP    127.0.0.1:1133         127.0.0.1:5354         ESTABLISHED
  TCP    127.0.0.1:5152         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:5152         127.0.0.1:1036         CLOSE_WAIT
  TCP    127.0.0.1:5354         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:5354         127.0.0.1:1128         ESTABLISHED
  TCP    127.0.0.1:5354         127.0.0.1:1129         ESTABLISHED
  TCP    127.0.0.1:5354         127.0.0.1:1130         ESTABLISHED
  TCP    127.0.0.1:5354         127.0.0.1:1131         ESTABLISHED
  TCP    127.0.0.1:5354         127.0.0.1:1132         ESTABLISHED
  TCP    127.0.0.1:5354         127.0.0.1:1133         ESTABLISHED
  TCP    127.0.0.1:27015        0.0.0.0:0              LISTENING
  TCP    127.0.0.1:27015        127.0.0.1:1028         ESTABLISHED
  TCP    127.0.0.1:27015        127.0.0.1:1127         ESTABLISHED
  TCP    192.168.10.2:139       0.0.0.0:0              LISTENING
  UDP    0.0.0.0:445            *:*
  UDP    0.0.0.0:500            *:*
  UDP    0.0.0.0:1025           *:*
  UDP    0.0.0.0:4500           *:*
  UDP    127.0.0.1:123          *:*
  UDP    127.0.0.1:1900         *:*
  UDP    192.168.10.2:123       *:*
  UDP    192.168.10.2:137       *:*
  UDP    192.168.10.2:138       *:*
  UDP    192.168.10.2:1900      *:*
  UDP    192.168.10.2:5353      *:*


and after:

>netstat -an

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING
  TCP    127.0.0.1:1032         127.0.0.1:1033         ESTABLISHED
  TCP    127.0.0.1:1033         127.0.0.1:1032         ESTABLISHED
  TCP    127.0.0.1:1034         127.0.0.1:1035         ESTABLISHED
  TCP    127.0.0.1:1035         127.0.0.1:1034         ESTABLISHED
  TCP    127.0.0.1:5152         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:5152         127.0.0.1:1036         CLOSE_WAIT
  TCP    192.168.10.2:139       0.0.0.0:0              LISTENING
  UDP    0.0.0.0:445            *:*
  UDP    192.168.10.2:137       *:*
  UDP    192.168.10.2:138       *:*
Title: Re: iTunes issues
Post by: Skuzzy on December 10, 2008, 01:42:47 PM
That is uglier than I thought it would be.
Title: Re: iTunes issues
Post by: RTHolmes on December 10, 2008, 01:53:01 PM
 :D
Title: Re: iTunes issues
Post by: Mace2004 on December 10, 2008, 05:23:24 PM
REHolms, did you kill all five of the processes Tigger lists for your "after" list?  Is the after list "normal" or are the connections still excessive?
Title: Re: iTunes issues
Post by: Getback on December 10, 2008, 05:29:38 PM
FYI heres another box running iTunes before FSAuto:

>netstat -an

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3689           0.0.0.0:0              LISTENING
  TCP    127.0.0.1:1027         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:1028         127.0.0.1:27015        ESTABLISHED
  TCP    127.0.0.1:1032         127.0.0.1:1033         ESTABLISHED
  TCP    127.0.0.1:1033         127.0.0.1:1032         ESTABLISHED
  TCP    127.0.0.1:1034         127.0.0.1:1035         ESTABLISHED
  TCP    127.0.0.1:1035         127.0.0.1:1034         ESTABLISHED
  TCP    127.0.0.1:1127         127.0.0.1:27015        ESTABLISHED
  TCP    127.0.0.1:1128         127.0.0.1:5354         ESTABLISHED
  TCP    127.0.0.1:1129         127.0.0.1:5354         ESTABLISHED
  TCP    127.0.0.1:1130         127.0.0.1:5354         ESTABLISHED
  TCP    127.0.0.1:1131         127.0.0.1:5354         ESTABLISHED
  TCP    127.0.0.1:1132         127.0.0.1:5354         ESTABLISHED
  TCP    127.0.0.1:1133         127.0.0.1:5354         ESTABLISHED
  TCP    127.0.0.1:5152         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:5152         127.0.0.1:1036         CLOSE_WAIT
  TCP    127.0.0.1:5354         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:5354         127.0.0.1:1128         ESTABLISHED
  TCP    127.0.0.1:5354         127.0.0.1:1129         ESTABLISHED
  TCP    127.0.0.1:5354         127.0.0.1:1130         ESTABLISHED
  TCP    127.0.0.1:5354         127.0.0.1:1131         ESTABLISHED
  TCP    127.0.0.1:5354         127.0.0.1:1132         ESTABLISHED
  TCP    127.0.0.1:5354         127.0.0.1:1133         ESTABLISHED
  TCP    127.0.0.1:27015        0.0.0.0:0              LISTENING
  TCP    127.0.0.1:27015        127.0.0.1:1028         ESTABLISHED
  TCP    127.0.0.1:27015        127.0.0.1:1127         ESTABLISHED
  TCP    192.168.10.2:139       0.0.0.0:0              LISTENING
  UDP    0.0.0.0:445            *:*
  UDP    0.0.0.0:500            *:*
  UDP    0.0.0.0:1025           *:*
  UDP    0.0.0.0:4500           *:*
  UDP    127.0.0.1:123          *:*
  UDP    127.0.0.1:1900         *:*
  UDP    192.168.10.2:123       *:*
  UDP    192.168.10.2:137       *:*
  UDP    192.168.10.2:138       *:*
  UDP    192.168.10.2:1900      *:*
  UDP    192.168.10.2:5353      *:*


and after:

>netstat -an

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING
  TCP    127.0.0.1:1032         127.0.0.1:1033         ESTABLISHED
  TCP    127.0.0.1:1033         127.0.0.1:1032         ESTABLISHED
  TCP    127.0.0.1:1034         127.0.0.1:1035         ESTABLISHED
  TCP    127.0.0.1:1035         127.0.0.1:1034         ESTABLISHED
  TCP    127.0.0.1:5152         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:5152         127.0.0.1:1036         CLOSE_WAIT
  TCP    192.168.10.2:139       0.0.0.0:0              LISTENING
  UDP    0.0.0.0:445            *:*
  UDP    192.168.10.2:137       *:*
  UDP    192.168.10.2:138       *:*


My Gawd!!
Title: Re: iTunes issues
Post by: Tigger29 on December 10, 2008, 11:17:38 PM
Holy bloatware Batman!  That's a HUGE difference...

Title: Re: iTunes issues
Post by: RTHolmes on December 11, 2008, 03:45:52 AM
ah I should say thats not just killing iTunes, its everything apart from stuff for AH so includes MS Update, RDP, OpenOffice, Java and a bunch of other stuff. Just a demo of FSAuto cleaning up a pretty standard XP install which happens to have iTunes on it.

AFAIK ITunes uses ports: 3689, 5353, 5354 and 27015

I use FSAutostart to kill the following:

Services:
Apple Mobile Device
Bonjour Service (now called Rendezvous)
iPod service

Programs:
AppleMobileDeviceHelper.exe
iTunes.exe
iTunesHelper.exe

:)
Title: Re: iTunes issues
Post by: Skuzzy on December 11, 2008, 05:42:16 AM
Here is what my stock Windows Xp install looks like.

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:139            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1026           0.0.0.0:139           ESTABLISHED
  UDP    0.0.0.0:445            *:*                   
  UDP    0.0.0.0:500            *:*                   
  UDP    0.0.0.0:1027           *:*                   
  UDP    0.0.0.0:1038           *:*                   
  UDP    0.0.0.0:4500           *:*                   
  UDP    0.0.0.0:123            *:*                   
  UDP    0.0.0.0:137            *:*                   
  UDP    0.0.0.0:138            *:*                   
  UDP    127.0.0.1:123          *:*                   
Title: Re: iTunes issues
Post by: Babalonian on December 11, 2008, 03:07:29 PM
FYI heres another box running iTunes before FSAuto:

>netstat -an

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3689           0.0.0.0:0              LISTENING
  TCP    127.0.0.1:1027         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:1028         127.0.0.1:27015        ESTABLISHED
  TCP    127.0.0.1:1032         127.0.0.1:1033         ESTABLISHED
  TCP    127.0.0.1:1033         127.0.0.1:1032         ESTABLISHED
  TCP    127.0.0.1:1034         127.0.0.1:1035         ESTABLISHED
  TCP    127.0.0.1:1035         127.0.0.1:1034         ESTABLISHED
  TCP    127.0.0.1:1127         127.0.0.1:27015        ESTABLISHED
  TCP    127.0.0.1:1128         127.0.0.1:5354         ESTABLISHED
  TCP    127.0.0.1:1129         127.0.0.1:5354         ESTABLISHED
  TCP    127.0.0.1:1130         127.0.0.1:5354         ESTABLISHED
  TCP    127.0.0.1:1131         127.0.0.1:5354         ESTABLISHED
  TCP    127.0.0.1:1132         127.0.0.1:5354         ESTABLISHED
  TCP    127.0.0.1:1133         127.0.0.1:5354         ESTABLISHED
  TCP    127.0.0.1:5152         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:5152         127.0.0.1:1036         CLOSE_WAIT
  TCP    127.0.0.1:5354         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:5354         127.0.0.1:1128         ESTABLISHED
  TCP    127.0.0.1:5354         127.0.0.1:1129         ESTABLISHED
  TCP    127.0.0.1:5354         127.0.0.1:1130         ESTABLISHED
  TCP    127.0.0.1:5354         127.0.0.1:1131         ESTABLISHED
  TCP    127.0.0.1:5354         127.0.0.1:1132         ESTABLISHED
  TCP    127.0.0.1:5354         127.0.0.1:1133         ESTABLISHED
  TCP    127.0.0.1:27015        0.0.0.0:0              LISTENING
  TCP    127.0.0.1:27015        127.0.0.1:1028         ESTABLISHED
  TCP    127.0.0.1:27015        127.0.0.1:1127         ESTABLISHED
  TCP    192.168.10.2:139       0.0.0.0:0              LISTENING
  UDP    0.0.0.0:445            *:*
  UDP    0.0.0.0:500            *:*
  UDP    0.0.0.0:1025           *:*
  UDP    0.0.0.0:4500           *:*
  UDP    127.0.0.1:123          *:*
  UDP    127.0.0.1:1900         *:*
  UDP    192.168.10.2:123       *:*
  UDP    192.168.10.2:137       *:*
  UDP    192.168.10.2:138       *:*
  UDP    192.168.10.2:1900      *:*
  UDP    192.168.10.2:5353      *:*


and after:

>netstat -an

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING
  TCP    127.0.0.1:1032         127.0.0.1:1033         ESTABLISHED
  TCP    127.0.0.1:1033         127.0.0.1:1032         ESTABLISHED
  TCP    127.0.0.1:1034         127.0.0.1:1035         ESTABLISHED
  TCP    127.0.0.1:1035         127.0.0.1:1034         ESTABLISHED
  TCP    127.0.0.1:5152         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:5152         127.0.0.1:1036         CLOSE_WAIT
  TCP    192.168.10.2:139       0.0.0.0:0              LISTENING
  UDP    0.0.0.0:445            *:*
  UDP    192.168.10.2:137       *:*
  UDP    192.168.10.2:138       *:*


That's normal imo, but yeah, bad.  My wife has managed a couple of times to tickle iTunes in the right way that it will kick every other computer connected on my network off, including mine :furious .  A friend suggested I netstat it once when it was acting up again, and I stopped counting at around line 50.  Apple... *shakes his head*.  Thanfully her ipod broke over a year ago and the Zune she replaced it with seems to be engineered much better since I've never had to get involved with it. 
Title: Re: iTunes issues
Post by: Skuzzy on December 11, 2008, 03:14:24 PM
Ever seen what Steam does to a NAT table?  It ain't pretty. 

iTunes does the same thing.  It can flood a NAT table to the point where no other computer on the LAN can get access to the network.

At least Steam can be turned off.  Apple loves to let all this stuff just pigpile in Windows.  Quicktime is no better.

Apple is fortunate most people do not know how things work or how they are supposed to work.
Title: Re: iTunes issues
Post by: RTHolmes on December 12, 2008, 09:03:45 AM
the only "network killing" i've heard iTunes be responsible for was in fact due to a crappy driver for intel wireless hardware. any other info on that?

given what the software achieves its pretty amazing there arent more problems with it, I mean what other widely used (and free, remember) PC software does: audio en/decoding, music library organisation, syncing attached hardware devices, downloading and updating firmware on attached hardware devices, online ordering, audio and video streaming from/to other networked PCs, audio and video streaming to networked hardware etc...

I'd say Apple are very unfortunate that most people dont know how things are supposed to work, if consumers were more clued up Apple would have most of the market share and MS would have gone bust years ago. :rolleyes:

Title: Re: iTunes issues
Post by: Skuzzy on December 12, 2008, 09:42:46 AM
Yes, but we are all stuck with Microsoft, like it or not.  Apple is an option and until they take 50% of the marketplace, they will always be an option.

Most people are not aware of how things should work, but there are only a handful of companies that actually prey on that.  Apple, Roxio, Norton, just to name a few.  Whether it is done intentionally, or by design, can only be speculated.

Freeware has always been a risk.  Yet, there are some very good freeware/shareware programs out there.  Look at Foxit.

I could care less what iTunes can do and I am not impressed with it.  The cost is far too high, even when it is free.

I am not going to be drawn into an Apple versus PC war here.  Apple's track record with PC based software is what it is.  iTunes hurts our game performance.  It hurts connections to our servers.  It is a huge resource, which should NOT be running all the time.
Title: Re: iTunes issues
Post by: fudgums on December 12, 2008, 11:41:02 AM
ok How do I get rid of it?
Title: Re: iTunes issues
Post by: RTHolmes on December 12, 2008, 12:40:25 PM
you dont have to, if you like using it you keep it and kill it with everything else unecessary when u want to play AH. :)

iTunes hurts game performance - well yes it does. any software running which isnt necessary for AH will hurt performance.

iTunes hurts connections to your servers - no it doesn't (unless youve found evidence of iTunes attempting connections to the AH servers). although it may effect networking at the client PC end. any server software running which isnt necessary for AH will effect network performance.

I'm sorry to bang on about this but iTunes is getting demonised here when its no different from any other software running on your PC. On a marginal system would you want to run eg. AV scanning, SBS web serving and Real Networks streaming server while rendering some video from After Effects at the same time as AH? Of course not. It doesn't mean that you shouldn't install any of these apps on the machine, just means you should set up FSAuto or an alternative to killemall before firing up AH. :)
Title: Re: iTunes issues
Post by: Skuzzy on December 12, 2008, 01:09:49 PM
It does indeed hurt connections to the servers due to the number of open network threads it runs.  On many client systems it can cause problems with connections to other services.  We also tested it here on a pretty high end system, and it indeed was causing warps and stutters in the game.

I cannot count how many systems I have had to deal with whose connection reliability was negatively impacted by iTunes running in the background.

Most Windows processes simply run the message loop when they are not the primary application.  iTunes runs as if it is the primary application all the time.  There is a difference.  It has open "listeners" running which will respond to an asynchronous network event.  That is just wrong.

You can defend it all you like.  If you like software that assumes it will be the only application running on the computer, then iTunes is for you.  If you like software that always has asynchronous network connections open to the Internet, which is a potential major security violation, then iTunes is a good one.  If you like software that should not be running all the time, to run all the time, then iTunes is a good one.

If it was a well behaved application that did not adversely affect what I do for a living, I would not care one way or another.  I guess we could change Aces High II to always hold a connection open to the Internet and keep our resources constantly loaded, even when the application is not needed.  If iTunes can get away with it, then why not?
Title: Re: iTunes issues
Post by: RTHolmes on December 12, 2008, 01:19:23 PM
It has open "listeners" running which will respond to an asynchronous network event.  That is just wrong. etc...

you just defined a server, which is one part of what iTunes is. how is that different from any other server app?


if you ran the example software suite I mentioned earlier I guarantee AH will warp and stutter too. surely its better to advise that for best performance you run eg. FSAuto and kill everything unecessary (iTunes, After Effects, Bittorrent whatever...)
Title: Re: iTunes issues
Post by: Skuzzy on December 12, 2008, 01:42:02 PM
Windows Vista/XP was never designed to be used as a server platform operating system.  It does not have the security features required to be a competent server OS.  It does not have the network stack design to handle being a server.  The OS's were not designed to do this task.
Title: Re: iTunes issues
Post by: Wuden on December 12, 2008, 09:38:47 PM
Common AH isn't the most resource demanding ap out there.

My Cpu temps don't even go up much when playing.

I wish i could play windowed so I could tell whats going on better but hell I play with Chrome, Firefox, Itunes, Picasa, Word and notepad open regularly and Can't tell the difference from just AH playing.

this Isn't Crysis .


Also I haven't found any other iTunes type music organization/player software around that is ANYWhere as polished as iTunes.

Whats even remotely close ??
Title: Re: iTunes issues
Post by: Mace2004 on December 12, 2008, 10:18:00 PM
Interesting.  I can kill AppleMobileDeviceService.exe but it comes back in a minute on its own.  This is with all the other apparent Apple related processes dead.  When it restarts itself it also opens a TCP connection.
Title: Re: iTunes issues
Post by: RTHolmes on December 13, 2008, 06:08:46 AM
thats strange, using FSAuto to kill the services and programs i mentioned earlier does it for me.

Ive heard Vista has a proper startup manager now for this kind of thing, anyone used it? The one in MacOS 9 was really useful - just reboot and select the set optimised for what you wanted to do (I had gaming, design, web server and general set up and ready to go.)

PS skuzzy agreed there, I wouldnt run a proper server on any MS OS, but even your stock XP install has 3 server processes running. enable remote desktop access, file and printer sharing, uPNP etc and you'll have a whole bunch of servers (listening ports) running on a machine which is generally regarded as a client rather than a server.
Title: Re: iTunes issues
Post by: Skuzzy on December 13, 2008, 06:27:00 AM
It should not be running as a listener, unless it is serving up files from your computer, in which case, it has no business running all the time, and certainly will randomly affect a game connection due to bandwidth usage.  If it never serves up a file from your computer, then it has absolutely no business running as a listener.  As a listener, it will respond to every script kiddy polling ports from the Internet.

If it was written properly, it would not have all those background processes running all the time, especially as a listener.

Why the heck does it have to have all those processes running all the time?  IT DOESN'T!!!  Why is that concept so hard to grasp?  Why would anyone want to defend it?  Can any of you actually answer the question without speculating?

"Oh yeah, it's cool.  It is using up resources in my computer even when I do not want it running, but whatever.  It's like the best thing since sliced bread.  Ya know?  What else can steal resources from my computer when I do not want it to?  Cool huh?"

I'll never get passed that mentality.  It makes absolutely no sense to me.  Would you like it if someone attached to your car on the freeway so they could use your gas?

Why people do not care about how invasive some programs are is beyond me.  Maybe you like people coming into your home and using your television so they do not have to use thiers.  I just do not get it.
Title: Re: iTunes issues
Post by: RTHolmes on December 13, 2008, 07:34:45 AM
oh I care - I'm personally responsible to the Financial Services Authority for the network I administer under a wide range of legislation from Data Protection Act to Financial Services Act. I screw up and I can go to jail, not just receive a bunch of irate phone calls and emails :uhoh


theres nothing shady going on here, the processes and listening ports are all there for a reason:

Apple Mobile Device:    listens for iPods, iPhones, AppleTV etc devices to be connected
Bonjour Service:    zero conf networking services discovery, for iTunes music library sharing, printer discovery etc.
iPod service:    communicates with iPod for syncing, firmware updates etc.

iTunes runs a few services because it does alot. If you dont need all that functionality and want to save the odd cpu cycle, just disable em.

I like watching TV, the fact that there is a tiny chance that someone might break into my house to steal it is not a big enough threat to stop me from owning and using a TV because I take basic precautions like locking my front door (NAT and SPI firewall) :)
Title: Re: iTunes issues
Post by: Skuzzy on December 13, 2008, 01:41:45 PM
Ok, I am beating my head against a wall.

You want to take the phone calls I have to take and listen to people complain about how the game is warpy, and they are running all these programs that steal resources away.  I actually talked to one guy who had no idea what iTunes was, but it was running on his computer because the OEM thought it would be a good idea to load it on there for him.

These are the people I deal with everyday.  They do not know what all this stuff is.  They do not care what it is.  They want to play the game and not have to deal with warp jumps.  They are frustrated.  They have over 70 processes running in the background and they do not know why or what they are.  What OEM's do to computers should be criminal.

Then they come to the Tech Support forum and read about how wonderful iTunes is and they do nothing about it.  No, they would argue about it instead.  Even though they have no idea what the impact can be.  We have tested iTunes.  It does and can cause warps.  This is not speculation.


No matter what anyone says about it.  iTunes does not have to RUN 24 HOURS A DAY 7 DAYS A WEEK!  That is my beef with it.  And that also puts in the ill-behaved category.  Nothing any of you have said has made it appropriate or acceptable for this software to HAVE TO RUN ALL THE TIME.
Title: Re: iTunes issues
Post by: moot on December 13, 2008, 02:00:20 PM
"Oh yeah, it's cool.  It is using up resources in my computer even when I do not want it running, but whatever.  It's like the best thing since sliced bread.  Ya know?  What else can steal resources from my computer when I do not want it to?  Cool huh?"
:rofl
Title: Re: iTunes issues
Post by: LLogann on December 13, 2008, 08:18:16 PM
Yeah it does.... As a rule I always go to task manager and close out ALL silly processes.  You'll notice the difference immediately

iTunes adds at least 5 new processes...

Title: Re: iTunes issues
Post by: TequilaChaser on December 14, 2008, 11:00:17 PM
Yeah it does.... As a rule I always go to task manager and close out ALL silly processes.  You'll notice the difference immediately


going to Start/run/ type in "services.msc"  ( without the quotes ) is a heck of alot better than using task manager ( just a FYI )

it will even give you different options ( manual/disable/automatic, etc ) on what to do with a process as well as show you what that process depends on and what other process or components depends on the main/primary dependent/component.....and gives you a definition of what the process is....... research it.....this really helps cleans up a bunch of processes not needed and is easier and safer than Task Manager and MSconfig........

YMMV
Title: Re: iTunes issues
Post by: moot on December 15, 2008, 05:15:38 AM
And if you ever need to figure out what a certain process is, type its name (e.g. ituneshelper.exe) in google.