This seems to be my exact issue.

Some background information:
In the two days I've had this Macbook, I was able to play WoW perfectly fine until this morning. Yesterday night, I quested in Shadowmoon Valley with no problems whatsoever. Logged back into SMV this morning, and could barely take a step without WoW crashing. The couple times I was able to move around, the map would definitely crash the game.

I haven't noticed any other problems with the Macbook aside from those with WoW.

Couple excerpts from the eight error logs:
=========================================================
Exception Raised!

App: /Applications/World of Warcraft/World of Warcraft.app
Exception: SIGSEGV
Error Code: 0x85100086
Time: 2007-12-28 14.15.34 EST

Error: signo: 11, Fault address: 0xc2c711de, code(1): Address not mapped to object.

Exception State: trapno=14 err=6 Fault address=0xc2c711de

=========================================================
Exception Raised!

App: /Applications/World of Warcraft/World of Warcraft.app
Exception: SIGBUS
Error Code: 0x85100086
Time: 2007-12-28 14.14.45 EST

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

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


Hardware Overview:

Model Name: MacBook
Model Identifier: MacBook3,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 4 MB
Memory: 4 GB
Bus Speed: 800 MHz
Boot ROM Version: MB31.008D.B00
SMC Version: 1.24f2
Sudden Motion Sensor:
State: Enabled

Intel GMA X3100:

Chipset Model: GMA X3100
Type: Display
Bus: Built-In
VRAM (Total): 144 MB
Vendor: Intel (0x8086)
Device ID: 0x2a02
Revision ID: 0x0003
Displays:
Color LCD:
Display Type: LCD
Resolution: 1280 x 800
Depth: 32-bit Color
Built-In: Yes
Core Image: Hardware Accelerated
Main Display: Yes
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Display Connector:
Status: No display connected

System Software Overview:

System Version: Mac OS X 10.5.1 (9B18)
Kernel Version: Darwin 9.1.0
Boot Volume: Macintosh HD
Boot Mode: Normal
Time since boot: 47 minutes

Edit: I just wanted to mention in case it was overlooked by anyone that I have actually upgraded my RAM to 4 gigs (third party) instead of the factory default 1 gig. Also, I can verify that windowed mode does help the crashing problem on my Mac pretty considerably, despite slowing down WoW a bit. Thank you guys for posting some techniques and addons that help.

And completely unrelated, happy New Year all!

I'm having a different problem occur. I've been able to play WoW without problems also and still can. But the other night I was in WSG. When I was killed, i was sent to the GY then the game crashed and gave me the error report. I have a link to the thread that i created earlier.

http://forums.worldofwarcraft.com/thread.html?topicId=3686750435&postId=36863889804&sid=1#0

EDIT: I've added the error report to the thread I made. I wasn't sure If I needed every one of those "thread" things so I left those out. Please let me know if I need them and I will edit them back into my thread.

I've been having this exact problem. I've found that opening the world map while windowed in these zones will not crash the game. It only seems to happen when I'm maximized in those specific areas. I've posted one of the error logs and all my system specs in this thread:

http://forums.worldofwarcraft.com/thread.html?topicId=3271184822&postId=33543357055&sid=1#2

I have also been having this exact problem. Got a Macbook for Christmas, and it would crash whenever I opened the map (I was in Terrokar, didn't get elsewhere to try it out) as well as having some random graphical glitches on the buttons.
Unfortunately, I uninstalled WoW on the Macbook and went back to playing it on my Powerbook G4 before I found this thread, so I don't have my error logs or system specs handy atm... my hardware specifications are virtually the same as Valmi's, except I have 2GB of memory instead of his 4.

As a side question, I know Blizzard is "looking into" this, but I read a bit online about the X3100 having problems with 3D graphics, so is this going to be an issue Blizzard can fix, or does the problem lie more with the X3100? Hopefully Blizzard can fix it, as I'd like to play on my shiny new computer, but either way thanks for the updates on this issue at least.

I've had similarity's to other peoples problems with my Mac. I've haven't had the map problems probably because, I haven't been in the forest but, I have experienced it quite often after I die which is very irriatating here is my thread I hope blizzard can help us Mac users on this one!
http://forums.worldofwarcraft.com/thread.html?topicId=3707961255&sid=1

I posted this earlier but I will post it in the appropriate forum now! The aforementioned issue is my exact problem. Here is my system info:

Hardware Overview:

Model Name: MacBook
Model Identifier: MacBook3,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.2 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 4 MB
Memory: 2 GB
Bus Speed: 800 MHz
Boot ROM Version: MB31.008D.B00
SMC Version: 1.24f2

Intel GMA X3100:

Chipset Model: GMA X3100
Type: Display
Bus: Built-In
VRAM (Total): 144 MB
Vendor: Intel (0x8086)
Device ID: 0x2a02
Revision ID: 0x0003
Displays:
Color LCD:
Display Type: LCD
Resolution: 1280 x 800
Depth: 32-bit Color
Built-In: Yes
Core Image: Hardware Accelerated
Main Display: Yes
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Display Connector:
Status: No display connected

System Software Overview:

System Version: Mac OS X 10.5.1 (9B18)
Kernel Version: Darwin 9.1.0
Boot Mode: Normal

http://forums.worldofwarcraft.com/thread.html?topicId=3547602895&sid=1

I didn't think you could play WoW with a Macbook. I tried it recently on a new black model (with the X3100) and couldn't get 30 fps with the settings down/off.

i am having the same problem on my brand new macbook3.1... It is frustrating. Hopefully this can be resolved soon because other than this problem my macbook runs wow almost perfectly, with the exception of the occasional graphics glitches (which all seem to fix themselves if i relaunch WoW).

keep me posted please, thank you.
___________________________________________

WoWBuild: 17561
Realm: Proudmoore [12.129.225.18:3724]
Local Zone: Legion Hold, Shadowmoon Valley
Local Player: Vonsteevan, 000000000023797F, (-3133.89,2895.65,101.696)

=========================================================
Exception Raised!

App: /Applications/World of Warcraft/World of Warcraft.app
Exception: SIGSEGV
Error Code: 0x85100086
Time: 2007-12-31 16.49.08 EST

Error: signo: 11, Fault address: 0x3f800009, code(1): Address not mapped to object.

Exception State: trapno=14 err=6 Fault address=0x3f800009


_________________________________
my macbook spec's:

Hardware Overview:

Model Name: MacBook
Model Identifier: MacBook3,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.2 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 4 MB
Memory: 2 GB
Bus Speed: 800 MHz
Boot ROM Version: MB31.008E.B01
SMC Version: 1.24f2


Intel GMA X3100:

Chipset Model: GMA X3100
Type: Display
Bus: Built-In
VRAM (Total): 144 MB
Vendor: Intel (0x8086)
Device ID: 0x2a02
Revision ID: 0x0003
Displays:
Color LCD:
Display Type: LCD
Resolution: 1280 x 800
Depth: 32-bit Color
Built-In: Yes
Core Image: Hardware Accelerated
Main Display: Yes
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Display Connector:
Status: No display connected


System Software Overview:

System Version: Mac OS X 10.5 (9A3115a)
Kernel Version: Darwin 9.0.0
Boot Volume: Macintosh HD
Boot Mode: Normal
Time since boot: 28 minutes

I just got the new black macbook running on leopard for Christmas, and besides a low fps due to it only having 1gb ram, it runs WoW great. This crash is the only problems i've found, and I hope you guys can help us out. I haven't tested the map error yet but I will after this post and I'll make sure to reply with the results. So far the crash seems completely random. The crash log below happened while in AV, but I've had others in Org, Shatt, and like I said it's pretty random. The only warning I get for an impending crash is graphical errors in the rendering of the landscape, usually on buildings or on the ground. Thanks again Blizz for addressing this problem and I hope you can supply us with a fix soon. : )

WoWBuild: 17561

Realm: Kel'Thuzad [206.17.111.96:3724]

Local Zone: Stonehearth Bunker, Alterac Valley

Local Player: Horix, 000000000313948F, (-145.673,-454.433,26.3975)

Locked Target: Stormpike Bowman, F040342E0000040C, (-173.069,-452.949,40.8372)

Last Enemy Target: Stormpike Bowman, F040342E0000040C, (-173.069,-452.949,40.8372)

Add Ons: ag_UnitFrames Bongos2 Bongos2_ActionBar Bongos2_CastBar Bongos2_MapBar Bongos2_RollBar Bongos2_Stats Bongos2_XP CT_BuffMod CT_MapMod


=========================================================
Exception Raised!

App: /Applications/World of Warcraft/World of Warcraft.app
Exception: SIGSEGV
Error Code: 0x85100086
Time: 2007-12-31 16.26.18 MST

Error: signo: 11, Fault address: 0x2a75c000, code(1): Address not mapped to object.

Exception State: trapno=14 err=6 Fault address=0x2a75c000


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

Hardware Overview:

Model Name: MacBook
Model Identifier: MacBook3,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.2 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 4 MB
Memory: 1 GB
Bus Speed: 800 MHz
Boot ROM Version: MB31.008D.B00
SMC Version: 1.24f2
Serial Number: ***********
Sudden Motion Sensor:
State: Enabled

Intel GMA X3100:

Chipset Model: GMA X3100
Type: Display
Bus: Built-In
VRAM (Total): 144 MB
Vendor: Intel (0x8086)
Device ID: 0x2a02
Revision ID: 0x0003
Displays:
Color LCD:
Display Type: LCD
Resolution: 1280 x 800
Depth: 32-bit Color
Built-In: Yes
Core Image: Hardware Accelerated
Main Display: Yes
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Display Connector:
Status: No display connected

System Software Overview:

System Version: Mac OS X 10.5.1 (9B18)
Kernel Version: Darwin 9.1.0
Boot Volume: Macintosh HD
Boot Mode: Normal
Computer Name: ********
User Name: **********
Time since boot: 4:58

I am thinking about getting a Macbook for my travel WoW needs. Any update on this issue? I am going to hold off until I hear it is corrected.

Alright so...after posting my initial log I logged back in and hearthed to Shatt. I flew into Terokkar forest and started opening my world map (using both the M button and the icon). I got on the ground, spammed my m button for a while, and nothing happened. I attacked a couple of mobs and ran around while spamming my map as well, and didn't produce the crash. Then I flew back to Shatt and caught a windrider to Shadowmoon Valley. I didn't open my map on the way there...but as soon as I landed I went up and clicked my map icon and BAM, it produced the crash. I'm going to try Nagrand next. The log is as follows:

WoWBuild: 17561

Realm: Kel'Thuzad [206.17.111.96:3724]

Local Zone: Shadowmoon Village, Shadowmoon Valley

Local Player: Horix, 000000000313948F, (-3003.3,2577.84,77.3308)

Add Ons: ag_UnitFrames Bongos2 Bongos2_ActionBar Bongos2_CastBar Bongos2_MapBar Bongos2_RollBar Bongos2_Stats Bongos2_XP CT_BuffMod CT_MapMod


=========================================================
Exception Raised!

App: /Applications/World of Warcraft/World of Warcraft.app
Exception: SIGSEGV
Error Code: 0x85100086
Time: 2007-12-31 17.14.21 MST

Error: signo: 11, Fault address: 0x2bef5000, code(1): Address not mapped to object.

Exception State: trapno=14 err=6 Fault address=0x2bef5000

Okay, i've been having the same problems but with the joy of having a couple of weeks off work for the holiday season I have been doing some testing the last couple of days. It was starting to drive me crazy with the disconnects (I got my gf and myself a macbook for xmas pretty much for wowing together).

It actually got so bad a couple of mornings ago I was finding it happening every 5 or 6 minutes - even when rolling a new character (dwarf).

This isn't an ideal fix but it has resolved it for me to about 95% of the problem. I say 95% because I'd hate to slap any guarantee down (that is for blue) but I'm going on the fact I've not disconnected for around 12 hours playing in outlands in various zones.

1. Because of the map problem I downloaded AlphaMap. I set this to replace my normal map in keybindings. I set opacity of the map to around 85-90%. I reduced the size of the map to take up the middle of the screen.

2. I used X-Perl to replace the player, pet, target and focus portraits. Note: I had to make sure the 3D portraits were NOT enabled. This actually heightened it for a while on my warlock character when the imp was out and when I was fighting the Scorch Imps in Skald, BE.

3. I used mappy to replace the in-game mini map.

4. I reduced some of the graphic sliders considerably (not ideal but I'd rather play right now while the devs resolve this), turned off ghost effect, spec water and shadows.

Now, call me crazy but these things worked for me. Maybe I've just been lucky - we will see. But hopefully - maybe, this will help to some degree.

Also to be noted, whenever the priest went to spirit of redemption it caused problems too for both me (i was a lock at the time) and the priest (gf) when in Z'F (Tanaris). There was a single occasion it didn't cause a problem.

Since these changes there has only been 1 crash between both of us and that was when I found myself at the spirit healer in Zanga following a nasty encounter in Slave Pens.

Hopefully this information will be of some help. I have submitted pretty much every report to Blizz that has been generated with the crash.

Thanks in advance for looking into this more - hope this helps folks in the meantime!

Cheers

Alright, I've completed my rounds around outland. After I produced a "successful" crash in Shadowmoon, I flew to Nagrand. This time I spammed my map buttons on the way there, and when I entered Nagrand it produced a crash while in flight. I rebooted WoW and waited until I landed, clicked my map again, and produced a crash. I flew to all the other zones, first Hellfire, then Zangermarsh, Blades Edge, and Netherstorm. All produced NO crash when spamming the map. I flew back to Shatt and tested Terokkar again, and couldn't produce a crash.

Now comes the interesting part, I entered Windowed mode (control+m) and tested all the regions again. NONE of them produce a crash if I'm in windowed mode. If I exit windowed mode into full screen while in Shadowmoon or Nagrand, and then press my M button or the map icon...it produces a crash immediately.

So, at least on my machine, windowed mode fixes the "map" related crashing in Shadowmoon and Nagrand. In fullscreen, the only areas I can force a crash using the map issue is Shadowmoon and Nagrand...ALL other Outland areas did not crash. Windowed mode DOES NOT fix the "random" crashes I get out of nowhere, and again, graphical errors in the terrain usually come up before this "random" crash. Both in fullscreen and windowed it occurs. I hope this helps, and if I can find any other reproducible crashes I'll make sure to reply.

---

Q u o t e:
Alright, I've completed my rounds around outland. After I produced a "successful" crash in Shadowmoon, I flew to Nagrand. This time I spammed my map buttons on the way there, and when I entered Nagrand it produced a crash while in flight. I rebooted WoW and waited until I landed, clicked my map again, and produced a crash. I flew to all the other zones, first Hellfire, then Zangermarsh, Blades Edge, and Netherstorm. All produced NO crash when spamming the map. I flew back to Shatt and tested Terokkar again, and couldn't produce a crash.

Now comes the interesting part, I entered Windowed mode (control+m) and tested all the regions again. NONE of them produce a crash if I'm in windowed mode. If I exit windowed mode into full screen while in Shadowmoon or Nagrand, and then press my M button or the map icon...it produces a crash immediately.

So, at least on my machine, windowed mode fixes the "map" related crashing in Shadowmoon and Nagrand. In fullscreen, the only areas I can force a crash using the map issue is Shadowmoon and Nagrand...ALL other Outland areas did not crash. Windowed mode DOES NOT fix the "random" crashes I get out of nowhere, and again, graphical errors in the terrain usually come up before this "random" crash. Both in fullscreen and windowed it occurs. I hope this helps, and if I can find any other reproducible crashes I'll make sure to reply.

---

I've noticed this exact same behavior. If you're trying to reproduce the crash in Terokkar, try the Bone Wastes. The rest of the zone seems fine to me.

Hmm... Has anyone experienced a problem with the GY or being in ghost form? Thats the problem I've had about 2 times but I was still told to use this forum though. I haven't been able to reproduce it either. (This happened both times while in WSG if that matters)

ok the only time i can force a crash now, using the settings mentioned above and being in windowed mode is by typing at the spirit healer - and even then it isn't every time.

---

Q u o t e:
ok the only time i can force a crash now, using the settings mentioned above and being in windowed mode is by typing at the spirit healer - and even then it isn't every time.

---

I'll have to try that... Thats exactly when the game crashed for me. I don't know if I had the "type" window up though.

This has happened to me as well. When I open my map in Terrokar and Nagrand, I crash. Although, it seems to be not such a prevalent issue in Windowed Mode. I also crashed once randomly in Terrokar.

Hardware:
Model Name: MacBook
Model Identifier: MacBook3,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.2 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 4 MB
Memory: 2 GB
Bus Speed: 800 MHz
Boot ROM Version: MB31.008D.B00
SMC Version: 1.24f2

Graphics/Displays:
Intel GMA X3100:
Chipset Model: GMA X3100
Type: Display
Bus: Built-In
VRAM (Total): 144 MB
Vendor: Intel (0x8086)
Device ID: 0x2a02
Revision ID: 0x0003
Displays:
Color LCD:
Display Type: LCD
Resolution: 1280 x 800
Depth: 32-bit Color
Built-In: Yes
Core Image: Hardware Accelerated
Main Display: Yes
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Display Connector:
Status: No display connected

Software:
System Version: Mac OS X 10.5.1 (9B18)
Kernel Version: Darwin 9.1.0
Boot Volume: Macintosh
Boot Mode: Normal



Error Log:

WoWBuild: 17561
Realm: Destromath [63.241.255.102:3724]
Local Zone: Terokkar Forest
Local Player: Duft, 00000000013A9221, (-3006.97,5987.46,5.51814)

=========================================================
Exception Raised!

App: /Applications/World of Warcraft/World of Warcraft.app
Exception: SIGSEGV
Error Code: 0x85100086
Time: 2007-12-30 21.54.40 EST

Error: signo: 11, Fault address: 0x3f5fe782, code(1): Address not mapped to object.

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

Registers:
eax=$00007890 ebx=$3f5fe772 ecx=$00000000 edx=$2249e000
edi=$0000001c esi=$3f5fe772 ebp=$bfffd038 esp=$bfffcfc0
eip=$005889f5 ss =$0000001f cs =$00000017 eflags=$00010206
ds =$0000001f es =$0000001f fs =$00000000 gs =$00000037

---------------------------------------------------------
Thread 0 (Current)
0 0x00030ceb
1 0x00031348
2 0x00039889
3 0x00004a93
4 0x00002e27
5 0x939c497b __sigtramp + 43
6 0x005889f5
7 0x00589f59
8 0x0058cc7b
9 0x0058847f
10 0x00307147
11 0x005861b8
12 0x00586cc4
13 0x00309d37
14 0x000b67a9
15 0x000b6daa
16 0x001bc7d0
17 0x001c1446
18 0x00388ad2
19 0x0038a044
20 0x005ad082
21 0x001629d1
22 0x0000b692
23 0x002a15d0
24 0x002a69a3
25 0x002a6c2e
26 0x00011b3e
27 0x000037a5
28 0x91089863 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1181
29 0x91088c9d SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 405
30 0x91088b02 _SendEventToEventTargetWithOptions + 58
31 0x910b781c ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 356
32 0x91089c1c DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2134
33 0x91088c9d SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 405
34 0x910a508e _SendEventToEventTarget + 52
35 0x91112444 _ToolboxEventDispatcher + 86
36 0x9110ec9e _RunApplicationEventLoop + 222
37 0x000038d6
38 0x000022a6
39 0x000021cd
40 0x00000001



Thread 1
0 0x9395face ___semwait_signal + 10
1 0x93989ced _pthread_cond_wait$UNIX2003 + 73
2 0x922cdf32 _glvmDoWork + 162
3 0x93989075 __pthread_start + 321
4 0x93988f32 _thread_start + 34
5 0x00000000



Thread 2
0 0x939588e6 _mach_msg_trap + 10
1 0x939600dc _mach_msg + 72
2 0x93950a5d _glcDebugListener + 349
3 0x93989075 __pthread_start + 321
4 0x93988f32 _thread_start + 34
5 0x00000000



Thread 3
0 0x93958946 _semaphore_timedwait_signal_trap + 10
1 0x9398a1cf __pthread_cond_wait + 1244
2 0x939d5177 _pthread_cond_timedwait + 47
3 0x0026cf85
4 0x000c4cdd
5 0x000f7a9b
6 0x000f7c88
7 0x91c0904d -[NSThread main] + 45
8 0x91c08bf4 ___NSThread__main__ + 308
9 0x93989075 __pthread_start + 321
10 0x93988f32 _thread_start + 34
11 0x00000000



Thread 4
0 0x9395892e _semaphore_wait_signal_trap + 10
1 0x9398a1e6 __pthread_cond_wait + 1267
2 0x939cfc4b _pthread_cond_wait + 48
3 0x0026d08b
4 0x0005e3eb
5 0x000f7a9b
6 0x000f7c88
7 0x91c0904d -[NSThread main] + 45
8 0x91c08bf4 ___NSThread__main__ + 308
9 0x93989075 __pthread_start + 321
10 0x93988f32 _thread_start + 34
11 0x00000000



Thread 5
0 0x939588e6 _mach_msg_trap + 10
1 0x939600dc _mach_msg + 72
2 0x964570fe _CFRunLoopRunSpecific + 1806
3 0x96457d38 _CFRunLoopRunInMode + 88
4 0x913a6464 HALRunLoop::OwnThread(void*) + 160
5 0x913a6300 CAPThread::Entry(CAPThread*) + 96
6 0x93989075 __pthread_start + 321
7 0x93988f32 _thread_start + 34
8 0x00000000



Thread 6
0 0x93958946 _semaphore_timedwait_signal_trap + 10
1 0x9398a1cf __pthread_cond_wait + 1244
2 0x9398ba53 _pthread_cond_timedwait_relative_np + 47
3 0x913b5a47 CAGuard::WaitFor(unsigned long long) + 213
4 0x913b7602 CAGuard::WaitUntil(unsigned long long) + 70
5 0x913b5da7 HP_IOThread::WorkLoop() + 759
6 0x913b5aab HP_IOThread::ThreadEntry(HP_IOThread*) + 17
7 0x913a6300 CAPThread::Entry(CAPThread*) + 96
8 0x93989075 __pthread_start + 321
9 0x93988f32 _thread_start + 34
10 0x00000000



Thread 7
0 0x93958a06 _mach_wait_until + 10
1 0x93688d13 _MPDelayUntil + 39
2 0x00658f2f
3 0x0067d39d
4 0x93989075 __pthread_start + 321
5 0x93988f32 _thread_start + 34
6 0x00000000



Thread 8
0 0x93958946 _semaphore_timedwait_signal_trap + 10
1 0x9398a1cf __pthread_cond_wait + 1244
2 0x939d5177 _pthread_cond_timedwait + 47
3 0x0026cf85
4 0x00294250
5 0x0029439a
6 0x000f7a9b
7 0x000f7c88
8 0x91c0904d -[NSThread main] + 45
9 0x91c08bf4 ___NSThread__main__ + 308
10 0x93989075 __pthread_start + 321
11 0x93988f32 _thread_start + 34
12 0x00000000



Thread 9
0 0x9398fb4e _select$DARWIN_EXTSN$NOCANCEL + 10
1 0x00293790
2 0x0029474e
3 0x000f7a9b
4 0x000f7c88
5 0x91c0904d -[NSThread main] + 45
6 0x91c08bf4 ___NSThread__main__ + 308
7 0x93989075 __pthread_start + 321
8 0x93988f32 _thread_start + 34
9 0x00000000



Thread 10
0 0x939588e6 _mach_msg_trap + 10
1 0x939600dc _mach_msg + 72
2 0x964570fe _CFRunLoopRunSpecific + 1806
3 0x96457d38 _CFRunLoopRunInMode + 88
4 0x91c6c560 +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 320
5 0x91c0904d -[NSThread main] + 45
6 0x91c08bf4 ___NSThread__main__ + 308
7 0x93989075 __pthread_start + 321
8 0x93988f32 _thread_start + 34
9 0x00000000



Thread 11
0 0x9395893a _semaphore_timedwait_trap + 10
1 0x936838a3 _MPWaitOnSemaphore + 125
2 0x00659259
3 0x0067d369
4 0x93989075 __pthread_start + 321
5 0x93988f32 _thread_start + 34
6 0x00000000



Thread 12
0 0x9395893a _semaphore_timedwait_trap + 10
1 0x936838a3 _MPWaitOnSemaphore + 125
2 0x00659259
3 0x0067d369
4 0x93989075 __pthread_start + 321
5 0x93988f32 _thread_start + 34
6 0x00000000



Thread 13
0 0x939a7f5a _select$DARWIN_EXTSN + 10
1 0x93989075 __pthread_start + 321
2 0x93988f32 _thread_start + 34
3 0x00000000



Thread 14
0 0x9395face ___semwait_signal + 10
1 0x93989ced _pthread_cond_wait$UNIX2003 + 73
2 0x12446b97 _gleCmdProcessor + 375
3 0x93989075 __pthread_start + 321
4 0x93988f32 _thread_start + 34
5 0x00000000



Thread 15
0 0x939588e6 _mach_msg_trap + 10
1 0x939600dc _mach_msg + 72
2 0x964570fe _CFRunLoopRunSpecific + 1806
3 0x96457d38 _CFRunLoopRunInMode + 88
4 0x90fb67ba CFURLCacheWorkerThread(void*) + 396
5 0x93989075 __pthread_start + 321
6 0x93988f32 _thread_start + 34
7 0x00000000



Thread 16
0 0x93958946 _semaphore_timedwait_signal_trap + 10
1 0x9398a1cf __pthread_cond_wait + 1244
2 0x939d5177 _pthread_cond_timedwait + 47
3 0x0026cf85
4 0x004f4382
5 0x000f7a9b
6 0x000f7c88
7 0x91c0904d -[NSThread main] + 45
8 0x91c08bf4 ___NSThread__main__ + 308
9 0x93989075 __pthread_start + 321
10 0x93988f32 _thread_start + 34
11 0x00000000



=========================================================