[Thain Esh Kelch]

After I've upgraded to 10.5, I'm getting the following error after more than an hour of playing online through battlenet: "Another application is using a needed game port. Quit other applications and try again." Quitting Warcraft and reentering fixes the problem for another few hours..

Anyone who has seen this problem, or has a solution?

[Dzaazd]

Thain Esh Kelch, on January 3rd 2008, 03:41 AM, said:

After I've upgraded to 10.5, I'm getting the following error after more than an hour of playing online through battlenet: "Another application is using a needed game port. Quit other applications and try again." Quitting Warcraft and reentering fixes the problem for another few hours..

Anyone who has seen this problem, or has a solution?

I have just gotten this problem myself. I have installed Warcraft 3 + TFT + patch to 1.21b. I got my (brand new) Macbook two days ago, upgraded to 4gigs of ram, and have installed xcode and a wikipedia widget. That's it---now you know my entire system configuration.

I was playing DotA version 6.51 on Bnet over wireless, and I did have safari opened in the background. The first time that I got the port problems Warcraft hung permanently when I tried to quit (so that I didn't know how to get out other than to reboot). I've just gotten the port problem again and after this post I will try to quit Warcraft. Wish me luck.

I've included as much info as I can in the hopes that we can find something in common. Like the previous post, I would love to hear of a solution.

Update:
After posting I switched back to WC3, which had been minimized. The program was dead without me having tried to quit, but I was able to force quit without issue.

[Thain Esh Kelch]

You seem to be having the exact same problems that I have. The quitting problem (Seen that on several machines over the years, and noone else but me seems to have them...) and the ports problem.

If its of any coincidence, I usually also only play DotA. I'll try to see if that has anything to do with it. Note, im also only playing on wireless.

Regarding your quit-crash-issue, a force quit *always* works for me!

[Bigfatlionman]

I have contacted Blizzard, Apple, Quest ( My ISP ) and and even Actionec ( the manufacturer of my modem ) I have no router I am using wireless. Representatives from apple told

me it is definitely not a network problem because I can connect to battle.net. Blizzard was not helpful at all , mac support will only correspond via emai l, and they

told me they could

not help me because there were not enough people calling in to say they have this problem . I have forwarded my ports, but that did not work either. When I looked

into the software

issue and checked whether any other ports were ACTUALLY being used by other application in my activity monitor there weren't . All I see in common is that some of us are using

wireless. But I was told that should not matter, by apple and blizzard. All i can say is that The Tech support people haven't figured it out. I have also tried deleteing registry files,

reinstalling, and looking for patches. failures. HELP!

[Thain Esh Kelch]

Okay, I'll try to send an email to Blizzard to see if they can start looking into this problem.. I'm having quite a few issues with Warcraft 3, but I also play it a lot.. 8)

[Bigfatlionman]

Blizzard started to contact me again, but they stopped talking to me the problem is still not fixed, this is bullsniff.

[Bigfatlionman]

did anyone figure out how to fix this yet????

[Thain Esh Kelch]

Haven't got a fix unfortunately. But I was just wondering, are you running Mac OS X 10.5 or 10.4?

[Pixeltoy]

This issue only exists with OS X10.5.
Using 10.4 there are NO port conflicts using wireless or cat5 cabling.
As of this week I have upgraded to 10.5 and while it is a beautiful OS this small (large?) issue is pissing me off! I get to play 1 game of DOTA and then I have to force quit Frozen Throne and restart it in order to play another game.

Frozen Throne needs an overhaul as well to make it Intel native. My Macbook Pro (Core Duo not 2 Duo) overheats and burns my palms each time I play!!!

And Blizzard and Apple are refusing to acknowledge this problem????

Just hope Starcraft 2 is worthwhile- can't play Starcraft any more due to all the hacking!

[Thain Esh Kelch]

W3:TFT *is* a universal binary! But I agree, it needs some serious CPU fixing.. O_o My MBP is starting to shop artifacts on the screen, due to overheating after playing a few hours of Warcraft... Hilarious.

[Pixeltoy]

Of late I play 20-30 minutes and then...CRASH! Fatal error. Report error to Blizzard! But the message never sends. Anyone else getting this?
Exception Raised!

App: Warcraft III
Exception: SIGBUS
Error Code: 0x85100084
Time: 2008-04-07 22.28.25 EST

Error: signo: 10, Fault address: 0x00000000, code(2): Nonexistent physical address.

Exception State: trapno=14 err=4 Fault address=0x00000000

Registers:
eax=$00000000 ebx=$002cd0f9 ecx=$107f11e0 edx=$0185e000
edi=$163c4bb0 esi=$107f1180 ebp=$b0226488 esp=$b0226330
eip=$002cd4f9 ss =$0000001f cs =$00000017 eflags=$00010246
ds =$0000001f es =$0000001f fs =$0000001f gs =$00000037

---------------------------------------------------------


Thread 0
0 0x91da69e6 DeInterlaceVU_ComponentDispatch+63bcf3
1 0x91dae1dc DeInterlaceVU_ComponentDispatch+6434e9
2 0x924c5b35 $ld$add$os10.4$_HIShapeContainsPoint+1cddaff
3 0x00010de9
4 0x000041c8
5 0x000031a6
6 0x0000bdcb
7 0x90501fc3 NotifyEventLoopObservers+091b
8 0x905013fd SendEventToEventTargetWithOptions+01d5
9 0x90501262 SendEventToEventTargetWithOptions+003a
10 0x90530520 GetEventDispatcherTarget+028a
11 0x9050237c NotifyEventLoopObservers+0cd4
12 0x905013fd SendEventToEventTargetWithOptions+01d5
13 0x9051de0e SendEventToEventTarget+0034
14 0x9058b110 GetMouse+0075
15 0x9058796a RunApplicationEventLoop+00de
16 0x0000bee6
17 0x00003a8b
18 0x0000643a
19 0x0000278a
20 0x000026a5
21


Thread 1
0 0x91da69e6 DeInterlaceVU_ComponentDispatch+63bcf3
1 0x91dae1dc DeInterlaceVU_ComponentDispatch+6434e9
2 0x011794c2 ape_agent+0134
3 0x91dd7c55 DeInterlaceVU_ComponentDispatch+66cf62
4 0x91dd7b12 DeInterlaceVU_ComponentDispatch+66ce1f
5


Thread 2
0 0x91da69e6 DeInterlaceVU_ComponentDispatch+63bcf3
1 0x91dae1dc DeInterlaceVU_ComponentDispatch+6434e9
2 0x924c5b35 $ld$add$os10.4$_HIShapeContainsPoint+1cddaff
3 0x00010de9
4 0x00010e08
5 0x000107c5
6 0x924ca409 $ld$add$os10.4$_HIShapeContainsPoint+1ce23d3
7 0x91dd7c55 DeInterlaceVU_ComponentDispatch+66cf62
8 0x91dd7b12 DeInterlaceVU_ComponentDispatch+66ce1f
9


Thread 3 (Crashed)
0 0x005d6b7f
1 0x002816da
2 0x00281c26
3 0x0001ca42
4 0x000062d9
5 0x91e135eb DeInterlaceVU_ComponentDispatch+6a88f8
6
7 0x002cea2a
8 0x002cf248
9 0x000aa014
10 0x003ec992
11 0x003ed07d
12 0x003ed803
13 0x00375ad7
14 0x00270976
15 0x00270c07
16 0x002713fc
17 0x001e3d84
18 0x00594d35
19 0x0059679a
20 0x00596d74
21 0x0000a837
22 0x00004b27
23 0x000107c5
24 0x924ca409 $ld$add$os10.4$_HIShapeContainsPoint+1ce23d3
25 0x91dd7c55 DeInterlaceVU_ComponentDispatch+66cf62
26 0x91dd7b12 DeInterlaceVU_ComponentDispatch+66ce1f
27


Thread 4
0 0x91da69e6 DeInterlaceVU_ComponentDispatch+63bcf3
1 0x91dae1dc DeInterlaceVU_ComponentDispatch+6434e9
2 0x924c5b35 $ld$add$os10.4$_HIShapeContainsPoint+1cddaff
3 0x924ca577 $ld$add$os10.4$_HIShapeContainsPoint+1ce2541
4 0x00010fa5
5 0x00010ffb
6 0x00278803
7 0x00019c7b
8 0x000ab079
9 0x000107c5
10 0x924ca409 $ld$add$os10.4$_HIShapeContainsPoint+1ce23d3
11 0x91dd7c55 DeInterlaceVU_ComponentDispatch+66cf62
12 0x91dd7b12 DeInterlaceVU_ComponentDispatch+66ce1f
13


Thread 5
0 0x91dadbce DeInterlaceVU_ComponentDispatch+642edb
1 0x91dd8ee6 DeInterlaceVU_ComponentDispatch+66e1f3
2 0x91dd88cd DeInterlaceVU_ComponentDispatch+66dbda
3 0x96cc4432 ATLU_DestroyThreadMemory+6b90f62
4 0x91dd7c55 DeInterlaceVU_ComponentDispatch+66cf62
5 0x91dd7b12 DeInterlaceVU_ComponentDispatch+66ce1f
6


Thread 6
0 0x91da69e6 DeInterlaceVU_ComponentDispatch+63bcf3
1 0x91dae1dc DeInterlaceVU_ComponentDispatch+6434e9
2 0x924c5b35 $ld$add$os10.4$_HIShapeContainsPoint+1cddaff
3 0x924ca577 $ld$add$os10.4$_HIShapeContainsPoint+1ce2541
4 0x00010fa5
5 0x00010ffb
6 0x00278803
7 0x005965df
8 0x000ab079
9 0x000107c5
10 0x924ca409 $ld$add$os10.4$_HIShapeContainsPoint+1ce23d3
11 0x91dd7c55 DeInterlaceVU_ComponentDispatch+66cf62
12 0x91dd7b12 DeInterlaceVU_ComponentDispatch+66ce1f
13


Thread 7
0 0x91da69e6 DeInterlaceVU_ComponentDispatch+63bcf3
1 0x91dae1dc DeInterlaceVU_ComponentDispatch+6434e9
2 0x93e5c0de $ld$add$os10.4$_HIShapeContainsPoint+36740a8
3 0x93e5cd18 $ld$add$os10.4$_HIShapeContainsPoint+3674ce2
4 0x92003464 ATLU_DestroyThreadMemory+1ecff94
5 0x92003300 ATLU_DestroyThreadMemory+1ecfe30
6 0x91dd7c55 DeInterlaceVU_ComponentDispatch+66cf62
7 0x91dd7b12 DeInterlaceVU_ComponentDispatch+66ce1f
8


Thread 8
0 0x91da6a46 DeInterlaceVU_ComponentDispatch+63bd53
1 0x91dd8daf DeInterlaceVU_ComponentDispatch+66e0bc
2 0x91dda633 DeInterlaceVU_ComponentDispatch+66f940
3 0x92012a47 ATLU_DestroyThreadMemory+1edf577
4 0x92014602 ATLU_DestroyThreadMemory+1ee1132
5 0x92012da7 ATLU_DestroyThreadMemory+1edf8d7
6 0x92012aab ATLU_DestroyThreadMemory+1edf5db
7 0x92003300 ATLU_DestroyThreadMemory+1ecfe30
8 0x91dd7c55 DeInterlaceVU_ComponentDispatch+66cf62
9 0x91dd7b12 DeInterlaceVU_ComponentDispatch+66ce1f
10


Thread 9
0 0x91da69e6 DeInterlaceVU_ComponentDispatch+63bcf3
1 0x91dae1dc DeInterlaceVU_ComponentDispatch+6434e9
2 0x924c5b35 $ld$add$os10.4$_HIShapeContainsPoint+1cddaff
3 0x924ca577 $ld$add$os10.4$_HIShapeContainsPoint+1ce2541
4 0x00010fa5
5 0x00010ffb
6 0x00278803
7 0x0065da51
8 0x000ab079
9 0x000107c5
10 0x924ca409 $ld$add$os10.4$_HIShapeContainsPoint+1ce23d3
11 0x91dd7c55 DeInterlaceVU_ComponentDispatch+66cf62
12 0x91dd7b12 DeInterlaceVU_ComponentDispatch+66ce1f
13


Thread 10
0 0x91da69e6 DeInterlaceVU_ComponentDispatch+63bcf3
1 0x91dae1dc DeInterlaceVU_ComponentDispatch+6434e9
2 0x924c5b35 $ld$add$os10.4$_HIShapeContainsPoint+1cddaff
3 0x00010de9
4 0x006bb558
5 0x006899d3
6 0x00582172
7 0x005867d8
8 0x000ab079
9 0x000107c5
10 0x924ca409 $ld$add$os10.4$_HIShapeContainsPoint+1ce23d3
11 0x91dd7c55 DeInterlaceVU_ComponentDispatch+66cf62
12 0x91dd7b12 DeInterlaceVU_ComponentDispatch+66ce1f
13


Thread 11
0 0x91da69e6 DeInterlaceVU_ComponentDispatch+63bcf3
1 0x91dae1dc DeInterlaceVU_ComponentDispatch+6434e9
2 0x924c5b35 $ld$add$os10.4$_HIShapeContainsPoint+1cddaff
3 0x924ca577 $ld$add$os10.4$_HIShapeContainsPoint+1ce2541
4 0x00010fa5
5 0x00010ffb
6 0x00278803
7 0x00585b6f
8 0x000ab079
9 0x000107c5
10 0x924ca409 $ld$add$os10.4$_HIShapeContainsPoint+1ce23d3
11 0x91dd7c55 DeInterlaceVU_ComponentDispatch+66cf62
12 0x91dd7b12 DeInterlaceVU_ComponentDispatch+66ce1f
13


Thread 12
0 0x91da69e6 DeInterlaceVU_ComponentDispatch+63bcf3
1 0x91dae1dc DeInterlaceVU_ComponentDispatch+6434e9
2 0x924c5b35 $ld$add$os10.4$_HIShapeContainsPoint+1cddaff
3 0x00010de9
4 0x006bb558
5 0x006899d3
6 0x00582172
7 0x00586cfb
8 0x000ab079
9 0x000107c5
10 0x924ca409 $ld$add$os10.4$_HIShapeContainsPoint+1ce23d3
11 0x91dd7c55 DeInterlaceVU_ComponentDispatch+66cf62
12 0x91dd7b12 DeInterlaceVU_ComponentDispatch+66ce1f
13


Thread 13
0 0x91da69e6 DeInterlaceVU_ComponentDispatch+63bcf3
1 0x91dae1dc DeInterlaceVU_ComponentDispatch+6434e9
2 0x924c5b35 $ld$add$os10.4$_HIShapeContainsPoint+1cddaff
3 0x924ca577 $ld$add$os10.4$_HIShapeContainsPoint+1ce2541
4 0x00010fa5
5 0x00010ffb
6 0x00278803
7 0x00586ffa
8 0x000ab079
9 0x000107c5
10 0x924ca409 $ld$add$os10.4$_HIShapeContainsPoint+1ce23d3
11 0x91dd7c55 DeInterlaceVU_ComponentDispatch+66cf62
12 0x91dd7b12 DeInterlaceVU_ComponentDispatch+66ce1f
13


Thread 14
0 0x91da6a46 DeInterlaceVU_ComponentDispatch+63bd53
1 0x91dd8daf DeInterlaceVU_ComponentDispatch+66e0bc
2 0x91dda633 DeInterlaceVU_ComponentDispatch+66f940
3 0x9247e92a $ld$add$os10.4$_HIShapeContainsPoint+1c968f4
4 0x9247e70a $ld$add$os10.4$_HIShapeContainsPoint+1c966d4
5 0x9081aaa2 $ld$add$os10.4$_HIShapeContainsPoint+32a6c
6 0x91dd7c55 DeInterlaceVU_ComponentDispatch+66cf62
7 0x91dd7b12 DeInterlaceVU_ComponentDispatch+66ce1f
8


Thread 15
0 0x91de9725 DeInterlaceVU_ComponentDispatch+67ea32
1 0x125b6ac9 CarbonselectThreadFunc+00cd
2 0x91dd7c55 DeInterlaceVU_ComponentDispatch+66cf62
3 0x91dd7b12 DeInterlaceVU_ComponentDispatch+66ce1f
4


Thread 16
0 0x91dadbce DeInterlaceVU_ComponentDispatch+642edb
1 0x91dd8ee6 DeInterlaceVU_ComponentDispatch+66e1f3
2 0x91dd88cd DeInterlaceVU_ComponentDispatch+66dbda
3 0x125b2938 CarbonOperationThreadFunc+00b1
4 0x91dd7c55 DeInterlaceVU_ComponentDispatch+66cf62
5 0x91dd7b12 DeInterlaceVU_ComponentDispatch+66ce1f
6


Thread 17
0 0x91dadbce DeInterlaceVU_ComponentDispatch+642edb
1 0x91dd8ee6 DeInterlaceVU_ComponentDispatch+66e1f3
2 0x91dd88cd DeInterlaceVU_ComponentDispatch+66dbda
3 0x125c2b9a CarbonInetOperThreadFunc+00d8
4 0x91dd7c55 DeInterlaceVU_ComponentDispatch+66cf62
5 0x91dd7b12 DeInterlaceVU_ComponentDispatch+66ce1f
6


Thread 18
0 0x91da6a46 DeInterlaceVU_ComponentDispatch+63bd53
1 0x91dd8daf DeInterlaceVU_ComponentDispatch+66e0bc
2 0x91dda633 DeInterlaceVU_ComponentDispatch+66f940
3 0x9247e92a $ld$add$os10.4$_HIShapeContainsPoint+1c968f4
4 0x9247e70a $ld$add$os10.4$_HIShapeContainsPoint+1c966d4
5 0x9247e40b $ld$add$os10.4$_HIShapeContainsPoint+1c963d5
6 0x91dd7c55 DeInterlaceVU_ComponentDispatch+66cf62
7 0x91dd7b12 DeInterlaceVU_ComponentDispatch+66ce1f
8


Thread 19
0 0x91da69e6 DeInterlaceVU_ComponentDispatch+63bcf3
1 0x91dae1dc DeInterlaceVU_ComponentDispatch+6434e9
2 0x924c5b35 $ld$add$os10.4$_HIShapeContainsPoint+1cddaff
3 0x924ca577 $ld$add$os10.4$_HIShapeContainsPoint+1ce2541
4 0x00010fa5
5 0x00010ffb
6 0x00278803
7 0x00581e28
8 0x000ab079
9 0x000107c5
10 0x924ca409 $ld$add$os10.4$_HIShapeContainsPoint+1ce23d3
11 0x91dd7c55 DeInterlaceVU_ComponentDispatch+66cf62
12 0x91dd7b12 DeInterlaceVU_ComponentDispatch+66ce1f
13


Thread 20
0 0x91da6a22 DeInterlaceVU_ComponentDispatch+63bd2f
1 0x90ea9eea $ld$add$os10.4$_HIShapeContainsPoint+6c1eb4
2 0x908a6a53 $ld$add$os10.4$_HIShapeContainsPoint+bea1d
3 0x90ea9ca8 $ld$add$os10.4$_HIShapeContainsPoint+6c1c72
4 0x91dd7c55 DeInterlaceVU_ComponentDispatch+66cf62
5 0x91dd7b12 DeInterlaceVU_ComponentDispatch+66ce1f
6
=========================================================

[Thain Esh Kelch]

I havent had that crash, but I did have another non-realated one yesterday. And I just mailed Blizzard to tell them their crash application doesn't work, but they didn't seem interested in it.. So I emailed them again, and now im waiting for a response.

[Sampster]

Pixeltoy, I've especially been having that problem of late with Foots vs Grunts games, and those are by far my favorite game types so its incredibly frustrating!

I've also been having the problem with 'another application using a needed game port' or whatever it is. Thain - please keep us posted if there's anything they tell you about. If there's an address I should email them at as well (the whole 'squeaky wheel gets the grease' thing) then I will.

[Thain Esh Kelch]

Well, you can try at macsupport@blizzard.com - But the last time I wrote them on the problem they just gave me the usual "Try reinstalling the software" - Duh, I've seen it on 3 different machines!

[fleskulf64]

Hi everyone, first post etc etc.

I, too, have had some trouble with the latest WC3 patch. I'm running Leopard on a Macbook 2.0 Ghz C2D, and since about a week ago, I've been getting kernel panics while playing the game. Curiously enough though, it only happens while playing DotA. After about 1-1,5 hrs, the game crashes and I get the usual "You must restart your computer" kernel panic screen.

I have also come across the "port in use" bug, although not as frequently as some of you are describing. In addition to this, I've also gotten "fatal error" crashes.

Any suggestions as to how to fix this? I have of course tried reinstalling WC3 (haven't gotten around to a full Leopard reinstall yet, but seriously.. all that for an error that should be very easy to fix?) It is also obviously WC3 related since I have never gotten a kernel panic before last week, and only WC3 triggers it. At first I thought it could be due to overheating, but I've been playing WC3 on this machine for over a year without experiencing this.. until now.

Any input is welcome and encouraged.

[Thain Esh Kelch]

Sounds strange that you are getting KPs, because I've always found War3 extremely stable (Apart from above mentioned issues), and DotA is also stable at the moment. I would actually assume that you have some flawed RAM?

In either case, could you post the first of a KP crashlog?

[fleskulf64]

Thain Esh Kelch, on April 26th 2008, 10:45 AM, said:

Sounds strange that you are getting KPs, because I've always found War3 extremely stable (Apart from above mentioned issues), and DotA is also stable at the moment. I would actually assume that you have some flawed RAM?

In either case, could you post the first of a KP crashlog?

I immediately thought of faulty hardware, but since the KPs only occur during WC3/DotA, I find this a bit strange. I have no trouble running several other memory-intensive applications, even at the same time.

In any case, I'll keep the info from the KP screen next time one occurs, and post the results here.

And thanks for answering my post, by the way.

[fleskulf64]

Ok, haven't been playing much lately, but tried last night and got a KP as usual. Here is the info from the crash report:

Fri May 9 03:10:57 2008
panic(cpu 0 caller 0x001A8C8A): Kernel trap at 0x0059d991, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x00000008, CR3: 0x01024000, CR4: 0x00000660
EAX: 0x00000000, EBX: 0xe00002c0, ECX: 0x00000000, EDX: 0x0194ff00
CR2: 0x00000008, EBP: 0x3433ff38, ESI: 0x03e61200, EDI: 0x0ba55800
EFL: 0x00010206, EIP: 0x0059d991, CS: 0x00000008, DS: 0x0bb90010
Error code: 0x00000000

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x3433fd28 : 0x12b0f7 (0x4581f4 0x3433fd5c 0x133230 0x0)
0x3433fd78 : 0x1a8c8a (0x461720 0x59d991 0xe 0x460ed0)
0x3433fe58 : 0x19ece5 (0x3433fe70 0x206 0x3433ff38 0x59d991)
0x3433fe68 : 0x59d991 (0xe 0xbb90048 0x34330010 0x3e0010)
0x3433ff38 : 0x350a08b5 (0xba55800 0xe0004004 0x0 0x0)
0x3433ff58 : 0x350a085e (0xba56500 0x350b1b28 0x3433ff78 0x1a236f)
0x3433ff78 : 0x13ea4a (0xba56500 0x0 0x1a236f 0x62392e8)
0x3433ffc8 : 0x19eadc (0x0 0x0 0x1a20b5 0x3d826b0)
Backtrace terminated-invalid frame pointer 0
Kernel loadable modules in backtrace (with dependencies):
com.Logitech.driver.HIDDevices(2.1.3)@0x35099000->0x350b1fff
dependency: com.apple.iokit.IOHIDFamily(1.5.2)@0x5ba000
dependency: com.apple.iokit.IOUSBFamily(3.0.8)@0x590000
com.apple.iokit.IOUSBFamily(3.0.8)@0x590000->0x5b7fff

BSD process name corresponding to current thread: kernel_task

Mac OS version:
9C7010

Kernel version:
Darwin Kernel Version 9.2.2: Tue Mar 4 21:17:34 PST 2008; root:xnu-1228.4.31~1/RELEASE_I386
System model name: MacBook2,1 (Mac-F4208CA9)



Any clue?

[Thain Esh Kelch]

Looks like its related to either a hardware mouse, or your logitech driver.

[fleskulf64]

Thain Esh Kelch, on May 11th 2008, 01:48 AM, said:

Looks like its related to either a hardware mouse, or your logitech driver.

Yeah, just noticed the bit about "Logitech" in the KP log, and when I think about it, my mouse is somewhat faulty, as it stops working for a few secs once in a while. How odd, something like that can actually crash a computer, haha. I'll try replacing it and see what happens.