Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Warcraft III and leopard
- Thread starter QCassidy352
- Start date
- Sort by reaction score
When I try to open WC3 it crashes after the opening movie, or if I try to skip it. what is going on??
afraid that's not a problem I've seen before...
Yes!
QCassidy352,
I am having the same exact problems you are. After my update to leopard been having problems with crashes in DotA. I have not yet retried to install War III yet... and I do have TM as well.. However, I know for a fact that it is not TM related because I've had some with and w/out. In fact several times I will have TFT lock up when i try to quit. I general minimize and then force quit because it locks up.
Have you found a solution yet?
I think I am going to try to re-install TFT and see if i get better results.
Macbook 2.0GHz Dual Intel 2GB RAM
QCassidy352,
I am having the same exact problems you are. After my update to leopard been having problems with crashes in DotA. I have not yet retried to install War III yet... and I do have TM as well.. However, I know for a fact that it is not TM related because I've had some with and w/out. In fact several times I will have TFT lock up when i try to quit. I general minimize and then force quit because it locks up.
Have you found a solution yet?
I think I am going to try to re-install TFT and see if i get better results.
Macbook 2.0GHz Dual Intel 2GB RAM
Interesting that you had the problem with dota and on a core duo MacBook (same as me). Coincidence?
Anyway, I reinstalled (actually copied the install from a machine that wasn't having problems) and the problem has not recurred. So try the reinstall; worked for me.
I had the same exact issue. I looked around and tried to reinstall WCIII.
I had issues uninstalling WCIII on Leopard, so I decided just to delete the Warcraft folder.
When I went to reinstall WCIII, which worked fine, but now it crashes on startup.
I get this error in the console:
Feb 15 16:00:45 MACPRO ReportCrash[298]: Formulating crash report for process Warcraft III[297]
Feb 15 16:00:45 MACPRO ReportCrash[298]: Saved crashreport to /Users/rafaelortiz/Library/Logs/CrashReporter/Warcraft III_2008-02-15-160045_MACPRO.crash using uid: 502 gid: 502, euid: 502 egid: 502
Feb 15 16:00:45 MACPRO com.apple.launchd[83] ([0x0-0x30030].com.blizzard.WarcraftIII[297]): Exited abnormally: Segmentation fault
And these problem details:
I had issues uninstalling WCIII on Leopard, so I decided just to delete the Warcraft folder.
When I went to reinstall WCIII, which worked fine, but now it crashes on startup.
I get this error in the console:
Feb 15 16:00:45 MACPRO ReportCrash[298]: Formulating crash report for process Warcraft III[297]
Feb 15 16:00:45 MACPRO ReportCrash[298]: Saved crashreport to /Users/rafaelortiz/Library/Logs/CrashReporter/Warcraft III_2008-02-15-160045_MACPRO.crash using uid: 502 gid: 502, euid: 502 egid: 502
Feb 15 16:00:45 MACPRO com.apple.launchd[83] ([0x0-0x30030].com.blizzard.WarcraftIII[297]): Exited abnormally: Segmentation fault
And these problem details:
Code:
Process: Warcraft III [323]
Path: /Applications/Warcraft III Folder/Warcraft III
Identifier: com.blizzard.WarcraftIII
Version: ??? (17268736)
Code Type: PPC (Translated)
Parent Process: launchd [83]
Date/Time: 2008-02-15 16:02:18.093 -0500
OS Version: Mac OS X 10.5.2 (9C31)
Report Version: 6
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000042353a34
Crashed Thread: 4
Thread 0:
0 translate 0xb815298f spin_lock_wrapper + 92003
1 translate 0xb8183603 CallPPCFunctionAtAddressInt + 169907
2 translate 0xb8186194 CallPPCFunctionAtAddressInt + 181060
3 translate 0xb80df67b 0xb8000000 + 915067
Thread 1:
0 ??? 0x800bb9e6 0 + 2148252134
1 ??? 0x800c31dc 0 + 2148282844
2 translate 0xb818b69a CallPPCFunctionAtAddressInt + 202826
3 ??? 0x800ecc55 0 + 2148453461
4 ??? 0x800ecb12 0 + 2148453138
Thread 2:
0 translate 0xb815298f spin_lock_wrapper + 92003
1 translate 0xb8183603 CallPPCFunctionAtAddressInt + 169907
2 translate 0xb8186194 CallPPCFunctionAtAddressInt + 181060
3 translate 0xb80df67b 0xb8000000 + 915067
Thread 3:
0 translate 0xb815283e spin_lock_wrapper + 91666
1 translate 0xb816e877 CallPPCFunctionAtAddressInt + 84519
2 translate 0xb80bd6fb 0xb8000000 + 775931
3 translate 0xb80b6b77 0xb8000000 + 748407
4 translate 0xb80d4530 0xb8000000 + 869680
5 translate 0xb813d2cf spin_lock_wrapper + 4259
Thread 4 Crashed:
0 translate 0xb80b6b97 0xb8000000 + 748439
1 translate 0xb80d4530 0xb8000000 + 869680
2 translate 0xb813c9e9 spin_lock_wrapper + 1981
Thread 4 crashed with X86 Thread State (32-bit):
eax: 0x42353a38 ebx: 0xb80b67e8 ecx: 0xb8229e50 edx: 0x42353a34
edi: 0xb8208980 esi: 0x80316830 ebp: 0xb019ee98 esp: 0xb019ee30
ss: 0x0000001f efl: 0x00010246 eip: 0xb80b6b97 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037
cr2: 0x42353a34
Binary Images:
0xb8000000 - 0xb81d7fe7 translate ??? (???) /usr/libexec/oah/translate
Translated Code Information:
Rosetta Version: 20.44
Args: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp /Applications/Warcraft III Folder/Warcraft III
Exception: EXC_BAD_ACCESS (0x0001)
Thread 0: (0xb009a83c, 0xb815298f)
0xa0696924: /usr/lib/libSystem.B.dylib : ___is_threaded + 0
0x93c815f0: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore : _YieldToThread + 532
0x84a1f4a4: No symbol
0x84a1e688: No symbol
0x84a1e75c: No symbol
0x93c8681c: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore : _CooperativeThread + 348
0x9349d3ac: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp : + 0
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x934128a0 ctr: 0x9340b970
r00: 0xffffffe1 r01: 0xf0080c60 r02: 0x00000013 r03: 0xf0080d0c
r04: 0x00000003 r05: 0x00000018 r06: 0x00000020 r07: 0x00003503
r08: 0x00000000 r09: 0x00000000 r10: 0x00000000 r11: 0xa069b5f4
r12: 0x9340b970 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x00000018
r24: 0xf0080d0c r25: 0x00000020 r26: 0x00003503 r27: 0x00000000
r28: 0x00000000 r29: 0x00000003 r30: 0x00000003 r31: 0x93c813e4
Thread 1: (0xb011cd60, 0xb815283e)
0x9344ee00: /usr/lib/libSystem.B.dylib : __pthread_cond_wait + 1260
0x93c325e8: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore : _TSWaitOnConditionTimedRelative + 244
0x93c323bc: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore : _TSWaitOnSemaphoreCommon + 432
0x93c32080: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore : AsyncFileThread(void*) + 68
0x9349d3ac: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp : + 0
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x9344ee40 ctr: 0x9340b9f0
r00: 0xffffffd9 r01: 0xf0101cb0 r02: 0xa0696924 r03: 0x00003b03
r04: 0x00003903 r05: 0x0000003c r06: 0x00000000 r07: 0x00000000
r08: 0x00000000 r09: 0x00000001 r10: 0xf0101e68 r11: 0xa069b9dc
r12: 0x9340b9f0 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0x93d12214 r22: 0x93d12214 r23: 0x00000000
r24: 0x00000000 r25: 0x00000001 r26: 0xf0101e68 r27: 0xa069e928
r28: 0xa076783c r29: 0xa0696924 r30: 0xa0767870 r31: 0x9344e928
Thread 2: Crashed (0xb019ee30, 0xb80b6b97)
0x42353a36: No symbol
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x42353a36 ctr: 0x00000000
r00: 0x42353a36 r01: 0xf0182910 r02: 0x003f6000 r03: 0x00000001
r04: 0x00160a67 r05: 0x00160a67 r06: 0x00000045 r07: 0x41413a36
r08: 0x0015dfe0 r09: 0x00000004 r10: 0x00000003 r11: 0x00000010
r12: 0x93415148 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000
r24: 0x00000000 r25: 0x00000000 r26: 0x00000000 r27: 0x00000000
r28: 0x31313434 r29: 0x35363535 r30: 0x3a314533 r31: 0x30454130
Thread 3: (0xb7fff41c, 0xb815298f)
0xa075bdec: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore : _gThreadMgrMutex + 0
0x93c815f0: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore : _YieldToThread + 532
0x84a1f4a4: No symbol
0x846a7b50: No symbol
0x846a5e38: No symbol
0x84a50950: No symbol
0x90ed4f6c: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox : DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1488
0x90ed4104: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox : SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 468
0x90ed3f20: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox : _SendEventToEventTargetWithOptions + 56
0x90f04828: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox : ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 312
0x90ed53c0: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox : DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2596
0x90ed4104: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox : SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 468
0x90ef10e4: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox : _SendEventToEventTarget + 56
0x90f5fec8: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox : _ToolboxEventDispatcher + 88
0x90f5c404: /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox : _RunApplicationEventLoop + 168
0x84a50794: No symbol
0x846a60ac: No symbol
0x846ad058: No symbol
0x852e4878: No symbol
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x934128a0 ctr: 0x9340b970
r00: 0xffffffe1 r01: 0xbfffe0c0 r02: 0x00000013 r03: 0xbfffe16c
r04: 0x00000003 r05: 0x00000018 r06: 0x00000020 r07: 0x00003103
r08: 0x00000000 r09: 0x00000000 r10: 0x00000000 r11: 0xa069b5f4
r12: 0x9340b970 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0xffffffff
r20: 0xbffff6f0 r21: 0xbffff548 r22: 0x00115520 r23: 0x00000018
r24: 0xbfffe16c r25: 0x00000020 r26: 0x00003103 r27: 0x00000000
r28: 0x00000000 r29: 0x00000003 r30: 0x00000003 r31: 0x93c813e4did you also delete the preferences file from the library? (~/library/preferences/com.blizzard.warcraftIII)
Still no fix
For the previous post, not only must you delete your WCIII folder, but u must also go into your library - preferences. and delete anything to have to do with battle.net and WCIII.
Also, reinstalling WCIII still got me no fix. Every-time I play I have to minimize before shutting down and then 99% of the time I end up force quitting.... However, I finally found a common anomaly... It only occurs when i play a battle.net game, more specifically DotA.
If anyone has any insight. It would be much appreciated. I am tired of the force quitting...
For the previous post, not only must you delete your WCIII folder, but u must also go into your library - preferences. and delete anything to have to do with battle.net and WCIII.
Also, reinstalling WCIII still got me no fix. Every-time I play I have to minimize before shutting down and then 99% of the time I end up force quitting.... However, I finally found a common anomaly... It only occurs when i play a battle.net game, more specifically DotA.
If anyone has any insight. It would be much appreciated. I am tired of the force quitting...
See here - http://us.blizzard.com/support/arti...oryId=2546&parentCategoryId=2542&pageNumber=1
And Jim, that freeze on quitting warcraft 3 is not to do with DotA, it is to do when you are on battle.net. It is a known issue which sadly has not been fixed in the most recent patch.
And Jim, that freeze on quitting warcraft 3 is not to do with DotA, it is to do when you are on battle.net. It is a known issue which sadly has not been fixed in the most recent patch.
Anyone have any news on the the damn port problems? Every few games it says the port needed is already in use and then I have to quit the game (which usually involves a forced quit, mind you) and start it again.
that's yet another issue that I have. Frankly, I've taken to playing on XP. I can host with listchecker, get all of the DotA sounds, don't have to force quit, and don't get the "port in use" error. That's a lot of advantages, and it's worth the reboot, IMO.
I make sure that when I'm quitting anything, I'm not in full screen mode. If I'm in full screen mode, I can't do anything when the game crashes, and then I'm just screwed. If it's not in full screen, I can force quit the game.
So if you play a game of dota you can hear the sounds like "first blood" or "killing spree?"
You can quit the game after playing on battle.net without having to force quit?
And you can (consistently) play multiple battle.net games in a row without getting a "port in use" error?
I have not seen the "port-error" yet but it might be because I often play only few games in a row on battle.net. I do have the problem with a complete lockup of my MacBookPro when I try to quit the game after playing on battle.net. Windows xp is a solution I use for gaming events, but since blizzard games are supposed to work on mac I would really enjoy playing them in OSX without rebooting. Windows xp stinks ugliness every time I boot into it. So if someone finds a solution I really would like to see it posted here.
I have also tried to play Starcraft: BroodWar in Leopard and I can't get the game to boot. It just jumps in the dock a few times after I click "Ok" in the startupdialog and then quits.
I do have the latest updates for all applications installed, including games.
I've read quite a number of posts on blizzard game problems with Leopard now and I really hope someone finds a fix for these errors soon. I also have the problem with writing capitals in rtf-formatting in Gmail with the new Safari 3.1 update to sum up my current apple-problems. This is the wrong thread for a discussion about that issue but if anyone finds a fix please send me a message or post a link here.
---------------------------------
OS X 10.5.2
2.4 Ghz Intel Core 2 Duo MacBook Pro
About 3 weeks since I switched to Mac and I love it more every day
I have also tried to play Starcraft: BroodWar in Leopard and I can't get the game to boot. It just jumps in the dock a few times after I click "Ok" in the startupdialog and then quits.
I do have the latest updates for all applications installed, including games.
I've read quite a number of posts on blizzard game problems with Leopard now and I really hope someone finds a fix for these errors soon. I also have the problem with writing capitals in rtf-formatting in Gmail with the new Safari 3.1 update to sum up my current apple-problems. This is the wrong thread for a discussion about that issue but if anyone finds a fix please send me a message or post a link here.
---------------------------------
OS X 10.5.2
2.4 Ghz Intel Core 2 Duo MacBook Pro
About 3 weeks since I switched to Mac and I love it more every day
I dont play DOTA so i can't say anything about that, but yes I can quit battle.net, and then the game without having to force quit.
Also I played 6 ladder games yesterday, in a row, and I didnt have to force quit
Did you do a clean install on to your MBP? I ask because I imported my install over from my previous mac. No idea why that should matter, but I don't know why else you'd be Ok while others are having problems...
I have a question not related to the original question but about WC3.
I just bought my first apple a few days ago (2.5 ghtz MBP) and I installed WC3 on it and updated everything.
My question is, is there anyway of playing the game without having the CD inserted? Thats going to be a bummer to have to carry that thing around with me. I have a legitamate copy of the game, just wishing there was a No-CD workaround that didnt involve making a 700MB disc image and putting it on my desktop. Anyone have any tips?
EDIT: Now that I look at it the update logs say that the patch failed...uhg. I wonder why.
I just bought my first apple a few days ago (2.5 ghtz MBP) and I installed WC3 on it and updated everything.
My question is, is there anyway of playing the game without having the CD inserted? Thats going to be a bummer to have to carry that thing around with me. I have a legitamate copy of the game, just wishing there was a No-CD workaround that didnt involve making a 700MB disc image and putting it on my desktop. Anyone have any tips?
EDIT: Now that I look at it the update logs say that the patch failed...uhg. I wonder why.
just update to 1.21b. That removed the requirement that you play with a cd. Don't you love blizzard?
Of course, that means you have to get the update to work. But once you solve that, you're set.
I did a clean install as well because this is my first Mac. I have all the newest updates. I doubt it would make a difference but, for what it's worth, I have the MacBook model before Santa Rosa. I don't see that being a cause.