MBP - TV
So I had this dream that I would be able to plug my Macbook Pro into any TV in the world and be able to use it for various and sundry things. I decided to act upon this idea. I discovered that my MBP has a Mini DisplayPort for video output. Great! I'm halfway there. So I search high and low for a Mini DisplayPort to Video adapter... Apple doesn't make one... and it seems no one else does either. So I, the educated and intelligent fellow that I am (if you don't mind my saying so), call my local Apple store and wait on hold for twenty minutes so that I may pose my question to someone who I assumed (makes an @$$ out of just me this time) would be able to answer my question appropriately.
This knowledgeable Apple employee told me that the best bet for making my wonderful Mini DisplayPort go to a Video outlet port would be to purchase a Mini Display to DVI adapter ( http://store.apple.com/us/product/MB570Z/A?mco=MTY3ODQ5OTY ) as well as a DVI to Video Adapter ( http://store.apple.com/us/product/M9267G/A?mco=MTY3ODQ5OTY ). So I do purchase these two adapters online and wait anxiously for them to arrive.
When they do arrive I make an amazing discovery: the DVI end of the Mini DisplayPort/DVI adapter does not match the DVI end of the DVI/Video Adapter... This is evident in the following two pictures if you look closely: http://storeimages.apple.com/1698/as-images.apple.com/is/image/AppleInc/M9267AV3?wid=326&hei=326&fmt=jpeg&qlt=95&op_sharpen=0&resMode=bicub&opusm=0.5,0.5,0,0&iccEmbed=0&layer=comp and http://storeimages.apple.com/1698/as-images.apple.com/is/image/AppleInc/MB570AV1?wid=326&hei=326&fmt=jpeg&qlt=95&op_sharpen=0&resMode=bicub&opusm=0.5,0.5,0,0&iccEmbed=0&layer=comp
The part of the DVI male portion that has the long flat prong also has four smaller metal prongs surrounding it.. the female portion has no receptacles for these 4 extra prongs... what the what?
I went by the Apple store today with my problem and received no helpful answer..
Why does no one make a Mini DisplayPort to Video adapter.. or why can I not find it.. and why does the DVI male portion not match DVI female portion?
I had a dream..
...as well as a VGA to HDMI adapter/converter?
Nope. You can (and should) go directly from mini-Displayport to HDMI:
http://store.apple.com/us/product/TY600VC/A?fnode=MTY1NDA5OQ&mco=MTY4NzA3MjU
This adapter will also feed audio through the HDMI cable if you have one of the April 2010 or later MBP models. If you have an earlier MPP, there is no audio feed through the mini-Displayport, and you will need a different MDP-HDMI adapter instead of the Griffin:
http://kanexlive.com/products/item.aspx?id=3495
The Kanex adapter feeds a video signal from the MDP and a 5.1-channel optical digital audio signal from the headphone port into a single HDMI cable, drawing its power from a USB port.
Similar Messages
-
Lock ups, beach balling 13" MBP
I go a new 13 inch MBP. Sometimes it locks up and i get the spinning beach ball for 10/15 seconds.
Anybody else with this problem??
ThanksThere is already an insanely long thread on this topic... Take a look here:
http://discussions.apple.com/thread.jspa?threadID=2054387&start=0&tstart=0 -
Ive been having issues since day 1 with my 2.4ghz C2D 17"MBP with highres screen...
Ive used fan-control software to put my fans up to there max speed with the lowest temp thresholds, but, im still having problems.
Under Windows XP (bootcamp) when I play Eve:Online for more than 10mins it will lock the laptop up solid, forcing me to hold down the power button to the the machine to shut down.
Having googled, it appears to be a heat related problem and I could buy something like a Coolermaster NotePalW1 to help keep it cool. Anyone got any other suggestions of things i can try to see if its a hardware or software problem?
Thanks, Darryn.
17" MBP, 24"iMac, Macpro (4x2.66) Mac OS X (10.4.10)In order to isolate the cause of these lock downs it is going to be necessary for you to backup your data first. Please let us know when this is done, and we can proceed?
-
MBP 15'' 2011 battery lasts only 3 hours!
Hi
I bought MBP 2011 15 inch last week and received it on Monday.
My configs are
Model Name: MacBook Pro
Model Identifier: MacBookPro8,2
Processor Name: Intel Core i7
Processor Speed: 2.2 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 6 MB
Memory: 4 GB
and I also upgraded to high resolution.
So far, I'm pretty much enjoying my new MBP
But I have one main concern with my new laptop's battery time.
The battry time is really really short!
When I first turned it on, it took 3 hours to drain the battery. (starting from 98% or so)
And I did calibration thing so that the battery runs more "efficiently"
Of course, I didn't expect that calibration would make the battery last longer, but no matter what,
I only get 3 hours of battery life and I'm not even doing something that would drain my battery fast.
I just do simple web surfing and word documenting on about 30-40% brightness (or even lower sometimes)
And I get only 3 hours of bettery time.
So is this because my MBP has four i7 cores or or what?
Previous MBP 15'' models seem to last at least around 5 hrs doing exactly same thing.
And considering that I have been using my MBP only for 5 days or so, I'm worried that the battery life will become even less!
Maybe like 2 hrs?
Is this a particular issue with my laptop, that I can return and exchange to new model or get fixed without fees?
Or is it just built this way that all the MBP 2011 15'' models have this kind of short battery life?OMG turning off the Bluetooth just gave me like extra 3 hours of battey time! (6 hrs total)
I didn't even know it was turned on in the first place because I never touched it.
I guess bluetooth is on as a default setting.
Thank you so much for advice.
I feel so stupid, but please be understanding since it's actually my first MacBook.
But I'm really glad to find out that I was wasting battery with bluetooth on, and now I can get better battery time.
Thanks once again! -
Mid '09 MBP bootup issue - flashing folder; possibly a fried drive?
Hi All,
This is my first post here. Today my 14 month old MBP 15-incher froze in the middle of some casual browsing/iTunes listening and decided to not respond to any mouse or keyboard input. I gave it some time to figure itself out and then after about 5 minutes of nothing, decided to force a shutdown by cutting power (10 second power button hold). Then upon my next boot the computer gives the chime, shows the grey screen (no logo), does nothing for ca. a minute and a half and then presents me with the glorious flashing questionmark-folder-whatever logo. Just great.
I reset the PRAM (option + command + p + r), tried Safe Booting (shift + boot), tried forcing the laptop to boot into the default os x drive/partition (x + boot), tried booting with GUI boot location selector (option + boot) and, when all mentioned practices failed, inserted a retail copy of snow leopard and booted the machine to the ODD.
Disk Utility confirmed my fears: the main HD has no partitions and the "First Aid" tab can't verify or repair the disk.
Help me out here, guys. Is my drive dead (and all my data gone)? Is this a "directory collapse"-style issue? I had one of those babies a month ago on an '07 white MacBook... a new HDD and two hours of data restoration work for $150 at a local Mac-centric repair shop fixed that issue. But this seems a little more serious.
I was two days away from activating a central Time Machine backup to the home-network-attached 2TB HDD, for both Mac laptops in the household. I was also two days away from getting a Crashplan.com family package (yes, I wanted double backup). Why 2 days from now? Because my Carbon Copy Cloned backup HD (a WD elements 1TB) died a week ago. As in, "started-puffing-out-smoke" died.
Perfect timing.
Ideas? Please?
<Edited by Host>I also suspect your internal HD has crashed. You can run Apple Hardware Test and then Google any error codes however I believe it's probably gone.
Without any backup yes your data is probably gone, there are data recovery services however they are extremely expensive.
If you purchased AppleCare you can take it an AASP for repair however they probably cannot do a thing about your data. If you are not covered by AppleCare of course the expense will be your however look at this as an opportunity to upgrade the internal HD to something with more storage or is faster.
Once you have the new HD installed you will need the original Snow Leopard Install Disks (or possibly your retail copy of SL) to format the new HD and re-install SL and the iLife applications.
Roger
Good luck,
Roger -
Mid-2009 MBP Has Been Hard Freezing, I think it may be the SSD or software?
Please read this fully so you don't end up suggesting something I've already tried.
I have the Mid-2009 version of the 13" MBP that I received in December 2009. Almost two years ago, I upgraded it to8 GB of RAM and a 256 GB SSD. Everything has been running smoothly until about 2 or so weeks ago. My computer has been having hard freezes, meaning, it's not simply an application freezing up; force quit doesn't work, the clock stops ticking, the whole system freezes. It was very predictable too. Whether i was watching youtube videos with flash, reading online articles without it (I have ad block) or doing something completely non-flash or web related, my computer would hard freeze after about an hour or two or so of use, requiring a hard reset (holding the power button until it turned off and then restarting).
I did some research on this and from what I initially found I thought it was problems with the motherboard. However, I found that to be odd because my motherboard was replaced by Apple in September 2012. I read somewhere to try a system hardware diagnostic test (press D upon start up). On the short hardware test, the one that only takes a few minutes, it passed without any problems. Then I tried the longer hardware test, the one that says takes more than an hour. I put that one on and left it alone. I came back every so often and checked on it and it was fine at first. The mouse responded and the test was showing some measurable progress. However I came back, and at 2 hours 11 minutes and 59 seconds into the hardware test, it froze without completing it.
Then I tried doing something everyone says to do when anything happens: I repaired disk permissions. I did that, and according to Disk utility everything went rather swimmingly. However, that didn't fix anything,in fact, it made things slightly worse. Ever since I reset disk permissions, everytime I open Safari, it freezes immediately, and that has only happened since I repaired disk permissions. My home page is about:blank, if anyone was wondering. I've only discovered this happening with Safari as of now. I switched Chrome as my primary web browser for now.
Being the resourceful person I am, I tried to isolate the problem. My sister, luckily, has an identical MBP. First, using target disk on my computer, I booted my SSD onto her computer - this is to see if the problem was HDD/SSD related or motherboard related. When I booted my SSD onto her computer the same problems occurred: Safari froze upon start up, and then computer would hard freeze after about two hours. However, when I booted her HDD onto my computer via target disk, there were no problems. Safari opened just fine and I used her computer for several hours without issue.
At this point, I was pretty sure it was the SSD, but I thought it was possibly a bad Sata cable or something. But nope. Last night, I switched harddrives completely. No target Disk. I put my SSD in her computer and put her HDD in my computer. I got the same results as target disk. It can't be the motherboard or memory, because both computers worked fine with my sisters harddrive. Only the computer booted off of the SSD would have these problems.
At this point I think it could be two possibilities
A) Either the SSD itself is starting to become defective
B) Some software component of my SSD is buggy
I think it could be something software related because why would Safari and safari only freeze after launch, but no other apps? Also something of note, these problems were happening, I tried to see if doing anything with software update would help, updated everything that needed to be updated, and these problems still occurred.
What do you guys think? anyone have an idea of what it could be? Any suggestions of how I handle this? Applecare is expired. I'm considering doing a clean install but I'm not fully backed up yet and I don't want to waste my time and have it not work. But I also don't want to buy a new hard drive or SSD and have it do the same things. And I'm not getting a new computer if the only problem with it is contained within the storage unit, whether that problem is within the software or hardware related.
Responses and suggestions would be highly appreciated, thanks.
EDIT: this information may be of interest: currently have 19.51 GB of available space (out of 256 GB). At one point, about a month and a half or so ago, my storage was as low as 9 or so GB free.
I am running OSX 10.6.8I have tried making a new user account like you suggested. It fixed the Safari problem; Safari opened and played video just fine. However, the computer still hard freezed after about 2 hours. I am about to back up my computer via time machine after this (hopefully it'll finish before it hard freezes again, I haven't backd up in more than a year). If that doesn't work, I guess I'll have to move folders individually onto an external. I will proceed after backup with a clean install as that is my only other option for now.
However, after a clean install, should I restore directly from time machine? I would think wiping the hard drive and replacing it with what's on time machine wouldn't solve the problem because the inherent corruption is being restored. However, what about just restoring my User folder? What would the process be for getting everything back to normal as quickly as possible? Do you know of any good ways to get my apps and other preferences back to normal ASAP without corrupting anything? Will I have to re-register anything? For example, I have Adobe CS4 that I received from my highschool IT department. I have since graduated, so I don't have the disc or any of the password codes. Would it be risky to restore the application support folder (because that's where the bug may lie)? Or if I just drag just drag apps, would that still work or is the application support necessary too? -
New MBP - wireless/internet access networking problem - a summary!
Greetings!
New MBP here, with all the trimmings (MacOS X 10.4.10 - Safari 3 Beta). New also to the Apple/MAC world
MBP >> wireless networking into a Linksys WRT54G router and >> thru HughesNet DW7000 Satellite Internet connection (not the fastest, but hey, the US and especially rural areas are NOT S. Korea when it comes to speedy internet connections!
Frankly, I bought into it for two reasons: First, hearing about the vaunted Mac a/v/ and doc/photo editing capabilities,... and about MacOS stability, etc... Well, it all needs a little work still: on the part of new users like me, but also probably on the part of the Apple/Mac people as well. 2nd reason I decided to purchase the MBP - i.e. ability to run Windows (I have not yet tried BootCanp, etc...: still resolving preliminary issues!). I still live in a heavy Win environment at my business - no other way of course!
Communications issues seem to still prevail: I am hanging out at several VERY HELPFUL forums (AppleDiscussionForum, MacRumorsForums, etc...) and the same issues keep popping up. Im my case, same as all above reported, with a few additional points, as follows:
1. Xmission errors: seem to be - at least in my case - a constant factor, regardless on how close/far i am from my wireless router. For example, I would be attempting to dwnload an upgrade (large)QT or MacOS file. i am barely into the dowmoad, and I already have several Read/Send errors. By the end of the download, I will have probably about 15 Rcv and 5 Send errors. Never gets quite that bad in my Win machines, I must mention. Anything to do here (I know, there are such things always affecting wireless com). AND, MOST importantly, how that this affect the effectiveness of the upgrade (I spotted same thing with MacOS 10.4.10 and Safari Beta 3 upgrade downloads!). Would it be likely that applying upgrades in such circumstances would screw up the OS??? Could OTOH such errors be automatically "compensated" by re-xmits from the source, and eventually the download would be OK? Because quite frankly, I do NOT know if my important upgrade download was OK to apply to the system, given those errors!!!
Also same thing with PING errors. Quite frequent when pinging another device on my network.
2. Quite often, accessing a site will proceed somehow OK, and then things will get stuck twd the end, as if some buffer somewhere gets overloaded??? Of course, as elsewhere reported, same can often happen with com getting stuck right over the "www" part of the URL!
3. AND, of course, the often reported "NO connection to the Internet", but computer shows good signal level and connection otherwise.
4. Strangely enough, seems that the Airport Extreme wifi card sort of "warms up the the internet" as one proceeds to start using it. It eventually picks up on a network, and often "improves" its connection over time!
5. Built in Airport Extreme seems to not exhibit up all immediately surrounding networks. Sensitivity issue?? iStumbler does.
6. iStumbler permanently posts noise level of 9% regardless of how close to my wireless router/broadband modem I am. Anyone uses iStumbler to monitor network traffic?
This is getting longuish: I just want to get over all those p*ant issues and get into putting my a/v stuff together!!
- Roger T
Thanks for just reading all this!. I am not sure it is all fixable (back to the Win "features" terminology, really meaning "bugs"??)Thanks, BDaqua. This support forum is quite well stocked: I have been perusing all its nooks and cranies!
On the www.dslreports.com - All things Mac - forum, I spotted a couple of mentions of the following type of infromation:
link: »www.hardmac.com/news/2007-07-27/#7039
- The first TechNote provides information concerning the Airport problem affecting the MBP Santa Rosa (but also other Mac Intel). When used on battery, the wireless connection drops and one can even experience kernel panic. Apple Centers are asked not to exchange affected notebook as this is due to a unidentified bug in the Atheros driver, and should be fixed in the future with a simple Airport system update. So for the moment, unfortunate users are asked to directly power their notebook when using wireless network, or using Ethernet connection when running on battery... in other words, turn your notebook into a desktop
to forum · permalink
I am wondering if you and folks on this close-to-Apple forum know anything about this. At least, we could just await remedy instead of messing around endlessly looking for solutions and... pondering as to whether it was a wise thing to purchase an expensive machine which happens to have trouble communicating online. After all, seems that the Mac folks are prone to spend MORE time online uploading/downloading music and videos instead of my being normally doing with the rest of my (Win) computers, i.e. work on customer lists, correspondence, inventories, accounting, data bases, etc....
So, seems to me we do have a pb and Apple might just save a few $$$ on silly ads and get to work on com instead. if nothing else to avoid the appearance of further - admittedly rather funny - ad-spoofs!
So back to your further inquiry. I run a wireless network from a HughesNet satellite modem, thru a Linksys WRT54GL wireless router, into some nearby office LANed desktops and point of sale equipment, to another neighbouring facility via wireless bridge, and to my Mac laptop. Distance from the laptop to the router: 50 ft max.
It all works surprizingly very well: up to 200kbps up and 1000 kbps down (in prime time, 150 up and 600 down). OK, my set up looks complex and incurring LOTS of activity. Actually, online activity is quite minimal and well scheduled - right now I am the only machine on the network online. Otherwise, our office processes online money wiring for customers among other things.
I'll try your DNS server choice on the Mac settings first. Will report accordingly.
Thanks for everything!
- Roger T -
Hello Sirs, I'm having a hard time connecting my MBP 13" (mid-2012) to my projector using my mini-display-VGA out adapter. But when I switch to Windows 7 (via bootcamp), it can easily be connected... Please help me with this problem. Thanks
Try connecting the Minidvi to the VGA and connect it all together, first try turning ing on the MBP, then connecting dvi to the the projector. Make sure your projector input is set for VGA. If noo joy invert the affored mentioned proceedure. You should see your image if not, try going to system preferences>displays, click display. Try readjusting the resolutions in display. reboot monitor.
-
I have a MBPro mid 2013 with 1 Thunderbolt port. Just bought a Mac monitor and want to daisy chain a PC monitor to it. Use a Mini DVI to VGA adapter from MBP to PC monitor. How do I daisy chain the 2 monitors?
Hall Palm Desert,
if your Mac monitor has Thunderbolt ports, and the PC monitor is on the end of the daisy chain, then you might be able to do it by connecting your PC monitor’s VGA cable to a Mini DisplayPort-to-VGA adapter (e.g. Apple, NewerTech), connecting that cable’s Mini DisplayPort end to one of the Mac monitor’s Thunderbolt ports, and then connecting a Thunderbolt cable between the other port on the Mac monitor and your MacBook Pro. -
Mini DVI to VGA incorrectly shipped with MBP instead of DVI to VGA
Has anyone else had a mini DVI to VGA adapter shipped with their macbook pro (2008) instead of a DVI to VGA adapter? I just needed to use it today and was told at the apple store that I had an adapter included with the computer. I went home to check and the adapter that was with the computer was a mini DVI to VGA adapter and the computer has a regular DVI output. I understand that later in 2008 the mac book pros were made with the mini DVI so I am thinking that there may have been a packaging error.......unusual for Apple???
Hi Tingrin,
Most likely an error when the machine was packaged for distribution. The MacBook Pro has never shipped with Mini DVI, it was a dual link DVI port until they went to Mini DisplayPort. The MacBook, however featured the Mini DVI.
I know Apple has ceased to ship the adapters with the MacBook Pro, to my knowledge they did around the time of the mid/late 2008 machines. I know with the first couple of generations (MBP) you actually got both a DVI and VGA adapter.
I'd contact Apple, inform of the discrepancy and I'm sure they'll make it right. -
Safari Fails to open and crashes after restoring MBP from Time Machine
I recently restored my information from Time Machine to a replacement MBP and every time I attempt to open Safari I get a message stating Safari failed to open. Any suggestions to solve this problem?
Here is the Error Message Details:
Process: Safari [580]
Path: /Applications/Safari.app/Contents/MacOS/Safari
Identifier: com.apple.Safari
Version: 5.1.7 (7534.57.4)
Build Info: WebBrowser-7534057004000000~7
Code Type: X86-64 (Native)
Parent Process: launchd [130]
Date/Time: 2012-09-13 16:24:14.957 +1000
OS Version: Mac OS X 10.7.4 (11E2617)
Report Version: 9
Interval Since Last Report: 153810 sec
Crashes Since Last Report: 1
Per-App Interval Since Last Report: 2 sec
Per-App Crashes Since Last Report: 1
Anonymous UUID: C94A602F-2BE0-446F-AFC5-70B44C1CC784
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
objc[580]: garbage collection is OFF
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Invalid parameter not satisfying: (index >= 0) && (index < [_itemArray count])'
*** First throw call stack:
0 CoreFoundation 0x00007fff91172f56 __exceptionPreprocess + 198
1 libobjc.A.dylib 0x00007fff914c5dee objc_exception_throw + 43
2 CoreFoundation 0x00007fff91172d8a +[NSException raise:format:arguments:] + 106
3 Foundation 0x00007fff8aacf71f -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 169
4 AppKit 0x00007fff8982bcdf -[NSMenu itemAtIndex:] + 165
5 AppKit 0x00007fff8982be38 -[NSMenu removeItemAtIndex:] + 63
6 Safari 0x0000000107e71c2e -[AppController awakeFromNib] + 387
7 CoreFoundation 0x00007fff91169fb1 -[NSObject performSelector:] + 49
8 CoreFoundation 0x00007fff91169f32 -[NSSet makeObjectsPerformSelector:] + 274
9 AppKit 0x00007fff898139ff -[NSIBObjectData nibInstantiateWithOwner:topLevelObjects:] + 1245
10 AppKit 0x00007fff89809f73 loadNib + 322
11 AppKit 0x00007fff89809470 +[NSBundle(NSNibLoading) _loadNibFile:nameTable:withZone:ownerBundle:] + 217
12 AppKit 0x00007fff8980938b +[NSBundle(NSNibLoading) loadNibFile:externalNameTable:withZone:] + 141
13 AppKit 0x00007fff898092ce +[NSBundle(NSNibLoading) loadNibNamed:owner:] + 364
14 AppKit 0x00007fff89a7a06f NSApplicationMain + 398
15 Safari 0x0000000108074806 SafariMain + 166
16 Safari 0x0000000107e60f24 Safari + 3876
terminate called throwing an exception
abort() called
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff88065ce2 __pthread_kill + 10
1 libsystem_c.dylib 0x00007fff9217a7d2 pthread_kill + 95
2 libsystem_c.dylib 0x00007fff9216ba7a abort + 143
3 libc++abi.dylib 0x00007fff8cbe47bc abort_message + 214
4 libc++abi.dylib 0x00007fff8cbe1fcf default_terminate() + 28
5 libobjc.A.dylib 0x00007fff914c6249 _objc_terminate + 94
6 libc++abi.dylib 0x00007fff8cbe2001 safe_handler_caller(void (*)()) + 11
7 libc++abi.dylib 0x00007fff8cbe205c std::terminate() + 16
8 libc++abi.dylib 0x00007fff8cbe3152 __cxa_throw + 114
9 libobjc.A.dylib 0x00007fff914c5f0a objc_exception_throw + 327
10 com.apple.CoreFoundation 0x00007fff91172d8a +[NSException raise:format:arguments:] + 106
11 com.apple.Foundation 0x00007fff8aacf71f -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 169
12 com.apple.AppKit 0x00007fff8982bcdf -[NSMenu itemAtIndex:] + 165
13 com.apple.AppKit 0x00007fff8982be38 -[NSMenu removeItemAtIndex:] + 63
14 com.apple.Safari.framework 0x0000000107e71c2e -[AppController awakeFromNib] + 387
15 com.apple.CoreFoundation 0x00007fff91169fb1 -[NSObject performSelector:] + 49
16 com.apple.CoreFoundation 0x00007fff91169f32 -[NSSet makeObjectsPerformSelector:] + 274
17 com.apple.AppKit 0x00007fff898139ff -[NSIBObjectData nibInstantiateWithOwner:topLevelObjects:] + 1245
18 com.apple.AppKit 0x00007fff89809f73 loadNib + 322
19 com.apple.AppKit 0x00007fff89809470 +[NSBundle(NSNibLoading) _loadNibFile:nameTable:withZone:ownerBundle:] + 217
20 com.apple.AppKit 0x00007fff8980938b +[NSBundle(NSNibLoading) loadNibFile:externalNameTable:withZone:] + 141
21 com.apple.AppKit 0x00007fff898092ce +[NSBundle(NSNibLoading) loadNibNamed:owner:] + 364
22 com.apple.AppKit 0x00007fff89a7a06f NSApplicationMain + 398
23 com.apple.Safari.framework 0x0000000108074806 SafariMain + 166
24 com.apple.Safari 0x0000000107e60f24 0x107e60000 + 3876
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff880667e6 kevent + 10
1 libdispatch.dylib 0x00007fff8b74178a _dispatch_mgr_invoke + 923
2 libdispatch.dylib 0x00007fff8b74031a _dispatch_mgr_thread + 54
Thread 2:
0 libsystem_kernel.dylib 0x00007fff88066192 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff9217a594 _pthread_wqthread + 758
2 libsystem_c.dylib 0x00007fff9217bb85 start_wqthread + 13
Thread 3:: Dispatch queue: com.apple.CFURLCACHE_work_queue
0 libsystem_kernel.dylib 0x00007fff880665b6 fsync + 10
1 libsqlite3.dylib 0x00007fff8e81ee38 unixSync + 72
2 libsqlite3.dylib 0x00007fff8e82c991 syncJournal + 705
3 libsqlite3.dylib 0x00007fff8e81da1e sqlite3PagerCommitPhaseOne + 1262
4 libsqlite3.dylib 0x00007fff8e80911e sqlite3BtreeCommitPhaseOne + 478
5 libsqlite3.dylib 0x00007fff8e808735 vdbeCommit + 981
6 libsqlite3.dylib 0x00007fff8e7cb55a sqlite3VdbeHalt + 4442
7 libsqlite3.dylib 0x00007fff8e7fd1a6 sqlite3VdbeExec + 51958
8 libsqlite3.dylib 0x00007fff8e7efa5b sqlite3_step + 1883
9 libsqlite3.dylib 0x00007fff8e7b2fb5 sqlite3_exec + 533
10 com.apple.CFNetwork 0x00007fff90e73b0c __CFURLCache::CreateTablesAndIndexes(sqlite3*) + 158
11 com.apple.CFNetwork 0x00007fff90e73f24 __CFURLCache::RecreateEmptyPersistentStoreOnDiskAndOpen_NoLock() + 184
12 com.apple.CFNetwork 0x00007fff90e743f1 __CFURLCache::RecreateEmptyPersistentStoreOnDiskAndOpen() + 75
13 com.apple.CFNetwork 0x00007fff90ddc55b __CFURLCache::OpenDatabase() + 221
14 com.apple.CFNetwork 0x00007fff90ddc040 ProcessCacheTasks(__CFURLCache*, bool) + 265
15 com.apple.CFNetwork 0x00007fff90ddba72 _ZL24_CFURLCacheTimerCallbackPv + 662
16 libdispatch.dylib 0x00007fff8b73fa86 _dispatch_call_block_and_release + 18
17 libdispatch.dylib 0x00007fff8b7412d6 _dispatch_queue_drain + 264
18 libdispatch.dylib 0x00007fff8b741132 _dispatch_queue_invoke + 54
19 libdispatch.dylib 0x00007fff8b74092c _dispatch_worker_thread2 + 198
20 libsystem_c.dylib 0x00007fff9217a3da _pthread_wqthread + 316
21 libsystem_c.dylib 0x00007fff9217bb85 start_wqthread + 13
Thread 4:: WebCore: IconDatabase
0 com.apple.WebCore 0x0000000109698030 ***::StringAppend<***::StringAppend<***::String, ***::String>, char const*> ***::operator+<***::String, ***::String, char const*>(***::StringAppend<***::String, ***::String> const&, char const*) + 0
1 com.apple.WebCore 0x0000000109086721 _ZN7WebCoreL20createDatabaseTablesERNS_14SQLiteDatabaseE + 673
2 com.apple.WebCore 0x0000000108f0e8ab WebCore::IconDatabase::performOpenInitialization() + 715
3 com.apple.WebCore 0x0000000108f0dc9a WebCore::IconDatabase::iconDatabaseSyncThread() + 314
4 com.apple.JavaScriptCore 0x000000010885411f _ZN3WTFL19wtfThreadEntryPointEPv + 15
5 libsystem_c.dylib 0x00007fff921788bf _pthread_start + 335
6 libsystem_c.dylib 0x00007fff9217bb75 thread_start + 13
Thread 5:: CoreAnimation render server
0 libsystem_kernel.dylib 0x00007fff8806467a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff88063d71 mach_msg + 73
2 com.apple.QuartzCore 0x00007fff8f692df5 CA::Render::Server::server_thread(void*) + 184
3 com.apple.QuartzCore 0x00007fff8f692d35 thread_fun + 24
4 libsystem_c.dylib 0x00007fff921788bf _pthread_start + 335
5 libsystem_c.dylib 0x00007fff9217bb75 thread_start + 13
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000000000006 rcx: 0x00007fff67a5e418 rdx: 0x0000000000000000
rdi: 0x000000000000060b rsi: 0x0000000000000006 rbp: 0x00007fff67a5e440 rsp: 0x00007fff67a5e418
r8: 0x00007fff7745bfb8 r9: 0x00007fff67a5dea8 r10: 0x00007fff88065d0a r11: 0xffffff80002dad60
r12: 0x00007f9cfc82bd90 r13: 0x0000000000000008 r14: 0x00007fff7745e960 r15: 0x00007fff67a5e590
rip: 0x00007fff88065ce2 rfl: 0x0000000000000246 cr2: 0x00007f9cfc0443fe
Logical CPU: 0
Binary Images:
0x107e60000 - 0x107e60fff com.apple.Safari (5.1.7 - 7534.57.4) <468C5147-26BF-321F-A7E6-42DA82AD4B1B> /Applications/Safari.app/Contents/MacOS/Safari
0x107e65000 - 0x1082ffff7 com.apple.Safari.framework (7536 - 7536.25) <C95F0D4E-6984-3D2F-B0BA-5D12A164EAC8> /System/Library/StagedFrameworks/Safari/Safari.framework/Safari
0x108621000 - 0x1088b0fff com.apple.JavaScriptCore (7536 - 7536.24) <C613502E-BC98-3269-A25C-4BDB2D87590B> /System/Library/StagedFrameworks/Safari/JavaScriptCore.framework/JavaScriptCore
0x108963000 - 0x108ae5ff7 com.apple.WebKit (7536 - 7536.25) <8D171955-A1CA-31AA-B701-B9D4F760B10B> /System/Library/StagedFrameworks/Safari/WebKit.framework/WebKit
0x108bd2000 - 0x108dabfff com.apple.WebKit2 (7536 - 7536.25) <15991DAF-D0C9-3D65-A96B-AF7428ADCC4E> /System/Library/StagedFrameworks/Safari/WebKit2.framework/WebKit2
0x108f0a000 - 0x109eafff7 com.apple.WebCore (7536 - 7536.24) <F2C26660-05D7-34A7-9158-9C3D21BEB32F> /System/Library/StagedFrameworks/Safari/WebCore.framework/WebCore
0x7fff67a60000 - 0x7fff67a94baf dyld (195.6 - ???) <C58DAD8A-4B00-3676-8637-93D6FDE73147> /usr/lib/dyld
0x7fff85a19000 - 0x7fff85a53fe7 com.apple.DebugSymbols (2.1 - 87) <ED2B177C-4146-3715-91DF-D99A8ED5449A> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbol s
0x7fff85a54000 - 0x7fff85a66ff7 libz.1.dylib (1.2.5 - compatibility 1.0.0) <30CBEF15-4978-3DED-8629-7109880A19D4> /usr/lib/libz.1.dylib
0x7fff86739000 - 0x7fff86b66fff libLAPACK.dylib (??? - ???) <C7456566-4B04-3971-8D62-DE0DEBE811B7> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libLAPACK.dylib
0x7fff86c18000 - 0x7fff86c41fff com.apple.CoreVideo (1.7 - 70.3) <9A9D4058-9935-3B0A-B1A6-27EB78D02249> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x7fff86c51000 - 0x7fff86c90fff com.apple.AE (527.7 - 527.7) <9B3F7EC2-EDE2-3123-BAA5-C36A09BA038E> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
0x7fff86c91000 - 0x7fff86cc4ff7 com.apple.GSS (2.2 - 2.0) <971395D0-B9D0-3FDE-B23F-6F9D0A2FB95F> /System/Library/Frameworks/GSS.framework/Versions/A/GSS
0x7fff86db2000 - 0x7fff86f0bfff com.apple.audio.toolbox.AudioToolbox (1.7.2 - 1.7.2) <E5B0E9FC-9823-33DD-BE31-C856CF9BB451> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x7fff86f0c000 - 0x7fff87180fff com.apple.CoreImage (7.98 - 1.0.1) <1E7BFFE3-4A46-317F-A1C0-A6FE040DE908> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/CoreImage .framework/Versions/A/CoreImage
0x7fff87382000 - 0x7fff87407ff7 com.apple.Heimdal (2.2 - 2.0) <A9FC8FF4-8D02-3D91-B409-AF19B72AEFDE> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal
0x7fff87634000 - 0x7fff87682fff libauto.dylib (??? - ???) <D8AC8458-DDD0-3939-8B96-B6CED81613EF> /usr/lib/libauto.dylib
0x7fff8774b000 - 0x7fff8774bfff com.apple.vecLib (3.7 - vecLib 3.7) <F968254A-2A06-3E2A-A587-151D7A2DB55A> /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
0x7fff8774c000 - 0x7fff87751fff libcache.dylib (47.0.0 - compatibility 1.0.0) <3D114C8A-AD1F-3C78-9E8C-B8F3810740E5> /usr/lib/system/libcache.dylib
0x7fff87ab0000 - 0x7fff87b04fff libFontRegistry.dylib (??? - ???) <2CCED595-0992-3A04-A8E8-887429652789> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/Resources/libFontRegistry.dylib
0x7fff87b05000 - 0x7fff87c0afff libFontParser.dylib (??? - ???) <DA05BC85-D79C-3F8E-A641-3E1E63B8E842> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/Resources/libFontParser.dylib
0x7fff87c0b000 - 0x7fff87c0cfff liblangid.dylib (??? - ???) <CACBE3C3-2F7B-3EED-B50E-EDB73F473B77> /usr/lib/liblangid.dylib
0x7fff87f4e000 - 0x7fff87f56fff libsystem_dnssd.dylib (??? - ???) <8A0F6F23-53C1-34FD-B641-4C0771C71E2A> /usr/lib/system/libsystem_dnssd.dylib
0x7fff87f57000 - 0x7fff87f73ff7 com.apple.GenerationalStorage (1.0 - 126.1) <509F52ED-E54B-3FEF-B3C2-759387B826E6> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/Gene rationalStorage
0x7fff87f87000 - 0x7fff8804eff7 com.apple.ColorSync (4.7.4 - 4.7.4) <F00820E4-7753-3F41-8D3D-95CD6F174886> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ColorSync.framework/Versions/A/ColorSync
0x7fff8804f000 - 0x7fff8806ffff libsystem_kernel.dylib (1699.31.2 - compatibility 1.0.0) <185823F1-409E-3AFD-93A9-C214013C17C8> /usr/lib/system/libsystem_kernel.dylib
0x7fff88070000 - 0x7fff88094fff com.apple.Kerberos (1.0 - 1) <5A114BAB-19C7-30B1-B9FB-F40019499734> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
0x7fff881d2000 - 0x7fff881d9fff com.apple.NetFS (4.0 - 4.0) <30AAE235-3F64-38BC-B0C9-271C8979C1C9> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
0x7fff881da000 - 0x7fff8827cfff com.apple.securityfoundation (5.0 - 55116) <1E062087-A9B1-3E38-8133-E9D282EA34B0> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoun dation
0x7fff8828b000 - 0x7fff88298ff7 libbz2.1.0.dylib (1.0.5 - compatibility 1.0.0) <DFAB8CA8-CC9D-3F58-8C12-CE120442AACD> /usr/lib/libbz2.1.0.dylib
0x7fff88299000 - 0x7fff885b5fff com.apple.CoreServices.CarbonCore (960.24 - 960.24) <CDCB53C0-D212-3485-A594-DDE33AAC5AF0> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x7fff885c5000 - 0x7fff886d1fff libcrypto.0.9.8.dylib (44.0.0 - compatibility 0.9.8) <557A7749-70EE-3ADF-BC3E-0A5E7DDCD8C1> /usr/lib/libcrypto.0.9.8.dylib
0x7fff886d2000 - 0x7fff886fdff7 libxslt.1.dylib (3.24.0 - compatibility 3.0.0) <E71220D3-8015-38EC-B97D-7FDB383C2BDC> /usr/lib/libxslt.1.dylib
0x7fff886fe000 - 0x7fff88834fff com.apple.vImage (5.1 - 5.1) <A08B7582-67BC-3EED-813A-4833645964A7> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.fr amework/Versions/A/vImage
0x7fff888bb000 - 0x7fff888bdff7 com.apple.print.framework.Print (7.4 - 247.3) <626C58D5-2841-3329-8C32-9F4A8353F3E7> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framewo rk/Versions/A/Print
0x7fff888be000 - 0x7fff88963fff com.apple.ink.framework (1.4 - 110) <93447D68-3018-30EB-9359-56385DDE4BA7> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework /Versions/A/Ink
0x7fff88964000 - 0x7fff88964fff com.apple.Carbon (153 - 153) <51D75B5A-3F04-32C9-BBA4-A96AF6E3FDFA> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x7fff88965000 - 0x7fff8896cfff libGFXShared.dylib (??? - ???) <0EA5DB50-D9AA-3BD5-9B1A-D5A82BD10E14> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.d ylib
0x7fff88dfe000 - 0x7fff88e15fff com.apple.CFOpenDirectory (10.7 - 146) <BBB7C97E-7B46-3286-9128-32B5D16B5CBE> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpen Directory.framework/Versions/A/CFOpenDirectory
0x7fff88e18000 - 0x7fff88e1dfff com.apple.OpenDirectory (10.7 - 146) <7960A302-F9AC-3F72-838E-3A382032DCA6> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
0x7fff88e1e000 - 0x7fff88e3bff7 com.apple.openscripting (1.3.3 - ???) <F5E34F54-CE85-334B-8F25-53581D43960C> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting .framework/Versions/A/OpenScripting
0x7fff88e3c000 - 0x7fff88eefff7 com.apple.CoreText (220.20.0 - ???) <4C3E0213-2627-37D1-8550-E30A0EA6C262> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreText.framework/Versions/A/CoreText
0x7fff88ef0000 - 0x7fff88ff2fff libxml2.2.dylib (10.3.0 - compatibility 10.0.0) <AFBB22B7-07AE-3F2E-B88C-70BEEBFB8A86> /usr/lib/libxml2.2.dylib
0x7fff88ff3000 - 0x7fff89047ff7 com.apple.ScalableUserInterface (1.0 - 1) <EB468227-3203-38C9-A5BC-E28576D507CF> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/ScalableU serInterface.framework/Versions/A/ScalableUserInterface
0x7fff89048000 - 0x7fff89272fe7 com.apple.CoreData (104.1 - 358.14) <1C100A86-EEDF-352E-8BC0-DFE82FF92362> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x7fff89383000 - 0x7fff89389fff com.apple.DiskArbitration (2.4.1 - 2.4.1) <22E77322-56E7-3730-9289-D8825A08408F> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x7fff8938a000 - 0x7fff89398fff com.apple.NetAuth (3.2 - 3.2) <B247BEAB-E3DA-3075-A2E5-BD3371AB0FA4> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
0x7fff89399000 - 0x7fff8939fff7 libunwind.dylib (30.0.0 - compatibility 1.0.0) <1E9C6C8C-CBE8-3F4B-A5B5-E03E3AB53231> /usr/lib/system/libunwind.dylib
0x7fff893a0000 - 0x7fff89416fff com.apple.CoreSymbolication (2.2 - 73.2) <126415E3-3A35-315B-B4B7-507CDBED0D58> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSy mbolication
0x7fff89417000 - 0x7fff8942cfff com.apple.speech.synthesis.framework (4.0.74 - 4.0.74) <4DD43F2F-7688-3028-868C-4E2876AFBF21> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x7fff8942d000 - 0x7fff8962ffff libicucore.A.dylib (46.1.0 - compatibility 1.0.0) <38CD6ED3-C8E4-3CCD-89AC-9C3198803101> /usr/lib/libicucore.A.dylib
0x7fff896d1000 - 0x7fff89713ff7 libcommonCrypto.dylib (55010.0.0 - compatibility 1.0.0) <A5B9778E-11C3-3F61-B740-1F2114E967FB> /usr/lib/system/libcommonCrypto.dylib
0x7fff89714000 - 0x7fff897f8fff com.apple.CoreServices.OSServices (478.46 - 478.46) <DAE95FD5-AA73-30E2-B563-EA2BDBD4D3CF> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x7fff897f9000 - 0x7fff8a3ffff7 com.apple.AppKit (6.7.3 - 1138.47) <2618FECE-B780-3682-B493-4200D473ED6F> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x7fff8a404000 - 0x7fff8a40afff libmacho.dylib (800.0.0 - compatibility 1.0.0) <548BAEB6-8C4C-3B0F-AB0C-7E1C960BCAB5> /usr/lib/system/libmacho.dylib
0x7fff8a40b000 - 0x7fff8a9effff libBLAS.dylib (??? - ???) <09028536-1215-324C-B7BD-384CF5DBC5D0> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libBLAS.dylib
0x7fff8a9f0000 - 0x7fff8aa03ff7 libCRFSuite.dylib (??? - ???) <322486D1-359C-3059-BF53-D4B038621E18> /usr/lib/libCRFSuite.dylib
0x7fff8aa04000 - 0x7fff8ad1dfff com.apple.Foundation (6.7.2 - 833.25) <F6584E06-7C8F-3422-AF84-3AA58EC67935> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fff8ae01000 - 0x7fff8ae5cff7 com.apple.opencl (2.0.16 - 2.0.16) <63F5AAE4-23DC-3279-AED7-6170D086C397> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
0x7fff8ae5d000 - 0x7fff8aeafff7 libGLU.dylib (??? - ???) <E9C325A6-D3D6-3C6A-A655-D2CB5BBEB992> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
0x7fff8aebe000 - 0x7fff8aee6fff com.apple.PerformanceAnalysis (1.11 - 11) <8D4C6382-DD92-37A2-BCFC-E89951320848> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/Perf ormanceAnalysis
0x7fff8aee7000 - 0x7fff8af57fff com.apple.datadetectorscore (3.0 - 179.4) <D14F635D-D403-3780-85C9-91EB0CA07F8E> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDe tectorsCore
0x7fff8af58000 - 0x7fff8af7efff com.apple.framework.familycontrols (3.0 - 300) <84E55A2E-643E-36E9-AFD8-CED667AF6B8E> /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/FamilyCon trols
0x7fff8b10b000 - 0x7fff8b1eaff7 com.apple.ImageIO.framework (3.1.2 - 3.1.2) <CDA0CC54-1442-3467-91D6-44456BD93733> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/ImageIO
0x7fff8b217000 - 0x7fff8b218ff7 libsystem_blocks.dylib (53.0.0 - compatibility 1.0.0) <8BCA214A-8992-34B2-A8B9-B74DEACA1869> /usr/lib/system/libsystem_blocks.dylib
0x7fff8b219000 - 0x7fff8b220fff libcopyfile.dylib (85.1.0 - compatibility 1.0.0) <65602684-33B1-32DE-802B-050CE07659AC> /usr/lib/system/libcopyfile.dylib
0x7fff8b221000 - 0x7fff8b72aff7 com.apple.RawCamera.bundle (3.14.0 - 646) <75A96BFC-1832-808B-F430-C4C9379C5A98> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera
0x7fff8b72f000 - 0x7fff8b73dff7 libkxld.dylib (??? - ???) <9F65E9DF-2A92-3CE2-BA34-247D392DAB48> /usr/lib/system/libkxld.dylib
0x7fff8b73e000 - 0x7fff8b74cfff libdispatch.dylib (187.9.0 - compatibility 1.0.0) <1D5BE322-A9B9-3BCE-8FAC-076FB07CF54A> /usr/lib/system/libdispatch.dylib
0x7fff8b8a6000 - 0x7fff8b8baff7 com.apple.LangAnalysis (1.7.0 - 1.7.0) <A7C58D71-6D4A-317D-AA06-D648B1F78573> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LangAnalysis.framework/Versions/A/LangAnalysis
0x7fff8b8bb000 - 0x7fff8b8dafff libresolv.9.dylib (46.1.0 - compatibility 1.0.0) <0635C52D-DD53-3721-A488-4C6E95607A74> /usr/lib/libresolv.9.dylib
0x7fff8b9a4000 - 0x7fff8b9e4ff7 libcups.2.dylib (2.9.0 - compatibility 2.0.0) <BDD11BE5-A9AB-347C-AB30-FDA1C5603E68> /usr/lib/libcups.2.dylib
0x7fff8b9e5000 - 0x7fff8bcceff7 com.apple.security (7.0 - 55148.1) <19F7B16B-B974-3274-886F-B8B2FA56032F> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x7fff8bcde000 - 0x7fff8c00aff7 com.apple.HIToolbox (1.9 - ???) <32527EBE-4E99-31F6-BBE7-60A796803905> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
0x7fff8c00b000 - 0x7fff8c016ff7 com.apple.speech.recognition.framework (4.0.21 - 4.0.21) <6540EAF2-E3BF-3D2E-B4C1-F106180D6F20> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecogni tion.framework/Versions/A/SpeechRecognition
0x7fff8c017000 - 0x7fff8c01cfff libcompiler_rt.dylib (6.0.0 - compatibility 1.0.0) <98ECD5F6-E85C-32A5-98CD-8911230CB66A> /usr/lib/system/libcompiler_rt.dylib
0x7fff8c1fa000 - 0x7fff8c1fafff com.apple.Accelerate (1.7 - Accelerate 1.7) <A42ACCF8-7C09-3891-B2B3-F6048A650BA2> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x7fff8c1fb000 - 0x7fff8c21bfff libPng.dylib (??? - ???) <F4D84592-C450-3076-88E9-8E6517C7EF33> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libPng.dylib
0x7fff8c277000 - 0x7fff8c280ff7 libsystem_notify.dylib (80.1.0 - compatibility 1.0.0) <A4D651E3-D1C6-3934-AD49-7A104FD14596> /usr/lib/system/libsystem_notify.dylib
0x7fff8c474000 - 0x7fff8c4dcff7 com.apple.audio.CoreAudio (4.0.3 - 4.0.3) <18776038-F2E5-360B-92BF-9263325E7F7D> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x7fff8c518000 - 0x7fff8c625fff libJP2.dylib (??? - ???) <5BE8CFA7-00C2-3BDE-BC20-5FF6DC18B415> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJP2.dylib
0x7fff8c626000 - 0x7fff8c627fff libdnsinfo.dylib (395.11.0 - compatibility 1.0.0) <853BAAA5-270F-3FDC-B025-D448DB72E1C3> /usr/lib/system/libdnsinfo.dylib
0x7fff8c914000 - 0x7fff8c914fff com.apple.Accelerate.vecLib (3.7 - vecLib 3.7) <4F7416F1-A069-3A39-B5F1-008279F6B819> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/vecLib
0x7fff8c9a7000 - 0x7fff8ca2bff7 com.apple.ApplicationServices.ATS (317.11.0 - ???) <46ED8F7A-01E9-3733-A531-3512DA8BC113> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/ATS
0x7fff8ca5d000 - 0x7fff8caa9ff7 com.apple.SystemConfiguration (1.11.3 - 1.11) <0A7F1982-B4EA-3424-A0C7-FE46C6224F03> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x7fff8caac000 - 0x7fff8caaffff libRadiance.dylib (??? - ???) <CD89D70D-F177-3BAE-8A26-644EA7D5E28E> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRadiance.dylib
0x7fff8cbc2000 - 0x7fff8cbc2fff com.apple.Cocoa (6.6 - ???) <9E3D4787-A2CE-38E0-BEF8-E5DA63B6E6A1> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x7fff8cbc3000 - 0x7fff8cbc4fff libunc.dylib (24.0.0 - compatibility 1.0.0) <0482C762-746D-37EB-A8C9-E1048CF70462> /usr/lib/system/libunc.dylib
0x7fff8cbcd000 - 0x7fff8cbcffff com.apple.TrustEvaluationAgent (2.0 - 1) <3087AE86-B57F-3D39-9885-C93DC6FD5163> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/Tru stEvaluationAgent
0x7fff8cbdc000 - 0x7fff8cbe7ff7 libc++abi.dylib (14.0.0 - compatibility 1.0.0) <8FF3D766-D678-36F6-84AC-423C878E6D14> /usr/lib/libc++abi.dylib
0x7fff8cbe8000 - 0x7fff8cbe9fff libDiagnosticMessagesClient.dylib (??? - ???) <3DCF577B-F126-302B-BCE2-4DB9A95B8598> /usr/lib/libDiagnosticMessagesClient.dylib
0x7fff8d42e000 - 0x7fff8d43dfff com.apple.opengl (1.8.0 - 1.8.0) <F487C903-3082-3528-916D-AC96AFF23927> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x7fff8d43e000 - 0x7fff8d441fff libCoreVMClient.dylib (??? - ???) <28CB0F3F-A202-391F-8CAC-FC9A1398A962> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClien t.dylib
0x7fff8d45e000 - 0x7fff8d46bfff libCSync.A.dylib (600.0.0 - compatibility 64.0.0) <36A15341-34AB-3D2B-96AD-15E198AA5180> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
0x7fff8d4f5000 - 0x7fff8d4f6ff7 libsystem_sandbox.dylib (??? - ???) <96D38E74-F18F-3CCB-A20B-E8E3ADC4E166> /usr/lib/system/libsystem_sandbox.dylib
0x7fff8d4f7000 - 0x7fff8d4fbfff libdyld.dylib (195.6.0 - compatibility 1.0.0) <FFC59565-64BD-3B37-90A4-E2C3A422CFC1> /usr/lib/system/libdyld.dylib
0x7fff8d4fc000 - 0x7fff8d55eff7 com.apple.Symbolication (1.3 - 91) <0945ACAF-AA0A-3D01-9960-72B51722EC1F> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolicat ion
0x7fff8d55f000 - 0x7fff8d571ff7 libbsm.0.dylib (??? - ???) <666E88F0-F8F3-3490-B688-2CF9418CB7E8> /usr/lib/libbsm.0.dylib
0x7fff8d5a8000 - 0x7fff8da6ffff FaceCoreLight (1.4.7 - compatibility 1.0.0) <BDD0E1DE-CF33-3AF8-B33B-4D1574CCC19D> /System/Library/PrivateFrameworks/FaceCoreLight.framework/Versions/A/FaceCoreLi ght
0x7fff8e7a8000 - 0x7fff8e8affe7 libsqlite3.dylib (9.6.0 - compatibility 9.0.0) <EE02BB01-64C9-304D-9719-A35F5CD6D04C> /usr/lib/libsqlite3.dylib
0x7fff8e8b0000 - 0x7fff8e919fff com.apple.coreui (1.2.2 - 165.10) <F427BF39-3E01-3DC6-A63D-BFC50FE6C72E> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
0x7fff8e960000 - 0x7fff8e96bfff com.apple.CommonAuth (2.2 - 2.0) <77E6F0D0-85B6-30B5-B99C-F57104DD2EBA> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth
0x7fff8e96c000 - 0x7fff8e96dff7 libremovefile.dylib (21.1.0 - compatibility 1.0.0) <8901B7EE-6CA0-31F3-BBFE-BB71C90B1E49> /usr/lib/system/libremovefile.dylib
0x7fff8e9d0000 - 0x7fff8ea66ff7 libvMisc.dylib (325.4.0 - compatibility 1.0.0) <C06C0706-3462-3F24-A8BE-4DA8076DE59F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib
0x7fff8ea67000 - 0x7fff8ea76fff libxar-nossl.dylib (??? - ???) <518C0791-AB8D-3E8A-BB40-D4F312704FE2> /usr/lib/libxar-nossl.dylib
0x7fff8ea77000 - 0x7fff8eaeafff libstdc++.6.dylib (52.0.0 - compatibility 7.0.0) <6BDD43E4-A4B1-379E-9ED5-8C713653DFF2> /usr/lib/libstdc++.6.dylib
0x7fff8eaeb000 - 0x7fff8eb1bff7 com.apple.DictionaryServices (1.2.1 - 158.2) <3107DEB8-A19E-3C51-8F2D-67CCE49FD401> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
0x7fff8ebad000 - 0x7fff8ebb3fff IOSurface (??? - ???) <77C6757B-D357-3E34-9424-48F962B5CC9C> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
0x7fff8ec3c000 - 0x7fff8ec41fff libGIF.dylib (??? - ???) <8763F67F-A881-30B6-B20E-D395B4D9FD58> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libGIF.dylib
0x7fff8ec4f000 - 0x7fff8ecc5fff libc++.1.dylib (28.1.0 - compatibility 1.0.0) <DA22E4D6-7F20-3BEA-9B89-2FBA735C2EE1> /usr/lib/libc++.1.dylib
0x7fff8edc8000 - 0x7fff8ee09fff com.apple.QD (3.40 - ???) <05970F98-B752-37AF-B577-2B940DF020A1> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ QD.framework/Versions/A/QD
0x7fff8ee0a000 - 0x7fff8ee45fff libsystem_info.dylib (??? - ???) <35F90252-2AE1-32C5-8D34-782C614D9639> /usr/lib/system/libsystem_info.dylib
0x7fff8ee46000 - 0x7fff8ee9efff libTIFF.dylib (??? - ???) <A0FF68DE-2935-30E7-B61C-4D9D70E14AD0> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x7fff8f564000 - 0x7fff8f58fff7 com.apple.CoreServicesInternal (113.17 - 113.17) <3D222F99-6155-363D-8B84-263B80500226> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/Cor eServicesInternal
0x7fff8f590000 - 0x7fff8f5fbff7 com.apple.framework.IOKit (2.0 - ???) <BA8FC1EB-0360-394F-9D6C-1D58BB187466> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x7fff8f690000 - 0x7fff8f830ff7 com.apple.QuartzCore (1.7 - 270.5) <E038F95C-B66D-3B04-AB32-5BB30FD7CB2A> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x7fff8f831000 - 0x7fff8f834ff7 com.apple.securityhi (4.0 - 1) <CA808DC8-7DCF-3B96-A6E8-C9A777C55DF9> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.fr amework/Versions/A/SecurityHI
0x7fff8f835000 - 0x7fff8f852fff libxpc.dylib (77.19.0 - compatibility 1.0.0) <9F57891B-D7EF-3050-BEDD-21E7C6668248> /usr/lib/system/libxpc.dylib
0x7fff8f853000 - 0x7fff8f858ff7 libsystem_network.dylib (??? - ???) <DD7492F9-39FB-3E73-9028-3E1027D012B9> /usr/lib/system/libsystem_network.dylib
0x7fff8f859000 - 0x7fff8f86ffff libGL.dylib (??? - ???) <E0183967-5EA6-3428-AC3B-0403A06F0E3F> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x7fff8f870000 - 0x7fff8f89dfe7 libSystem.B.dylib (159.1.0 - compatibility 1.0.0) <BD83ECD7-B044-364F-9392-9AE1FB3BBBD6> /usr/lib/libSystem.B.dylib
0x7fff8f89e000 - 0x7fff8f8fefff libvDSP.dylib (325.4.0 - compatibility 1.0.0) <1E3EEDA7-1DC6-3593-9DED-0BAFA0972A76> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvDSP.dylib
0x7fff8f964000 - 0x7fff8fa59fff libiconv.2.dylib (7.0.0 - compatibility 7.0.0) <5C40E880-0706-378F-B864-3C2BD922D926> /usr/lib/libiconv.2.dylib
0x7fff8fa5a000 - 0x7fff8fa64ff7 liblaunch.dylib (392.38.0 - compatibility 1.0.0) <6ECB7F19-B384-32C1-8652-2463C1CF4815> /usr/lib/system/liblaunch.dylib
0x7fff8fab3000 - 0x7fff8faf3fff libtidy.A.dylib (??? - ???) <E500CDB9-C010-3B1A-B995-774EE64F39BE> /usr/lib/libtidy.A.dylib
0x7fff8ffc6000 - 0x7fff8fffbfff com.apple.securityinterface (5.0 - 55022.4) <DAAEC695-EB88-311E-B929-B4CD9073924E> /System/Library/Frameworks/SecurityInterface.framework/Versions/A/SecurityInter face
0x7fff8fffc000 - 0x7fff90114fff com.apple.DesktopServices (1.6.4 - 1.6.4) <E1A724B2-0DCD-338B-86E2-76AB498DBA2E> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
0x7fff90119000 - 0x7fff9011cfff com.apple.help (1.3.2 - 42) <416BA8D2-9A2F-3F07-9E6B-E1231A92AAC0> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framewor k/Versions/A/Help
0x7fff9011d000 - 0x7fff9011ffff libquarantine.dylib (36.6.0 - compatibility 1.0.0) <0EBF714B-4B69-3E1F-9A7D-6BBC2AACB310> /usr/lib/system/libquarantine.dylib
0x7fff90167000 - 0x7fff90b04b47 com.apple.CoreGraphics (1.600.0 - ???) <C08FBA1B-E6C0-3020-AD4D-3A041734577D> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
0x7fff90b05000 - 0x7fff90b2eff7 com.apple.framework.Apple80211 (7.4 - 740.2) <341665EC-C964-34E0-92E1-743A66F94A44> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211
0x7fff90be8000 - 0x7fff90bedfff libpam.2.dylib (3.0.0 - compatibility 3.0.0) <D952F17B-200A-3A23-B9B2-7C1F7AC19189> /usr/lib/libpam.2.dylib
0x7fff90bfa000 - 0x7fff90bfcfff libCVMSPluginSupport.dylib (??? - ???) <CBAE2CCA-3B42-328E-8FA5-5EF22622EAEB> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginS upport.dylib
0x7fff90bfd000 - 0x7fff90bfdfff libkeymgr.dylib (23.0.0 - compatibility 1.0.0) <61EFED6A-A407-301E-B454-CD18314F0075> /usr/lib/system/libkeymgr.dylib
0x7fff90bfe000 - 0x7fff90c98ff7 com.apple.SearchKit (1.4.0 - 1.4.0) <C5585E08-76A0-34E0-B92C-22BA9D3E083C> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
0x7fff90ce0000 - 0x7fff90ce7ff7 com.apple.CommerceCore (1.0 - 17) <95285481-4162-308B-85E9-E0A47D4F3766> /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/C ommerceCore.framework/Versions/A/CommerceCore
0x7fff90ce8000 - 0x7fff90cfffff com.apple.MultitouchSupport.framework (231.4 - 231.4) <10A978D1-8781-33F0-BE45-60C9171F7278> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/Multit ouchSupport
0x7fff90d00000 - 0x7fff90d29fff libJPEG.dylib (??? - ???) <64D079F9-256A-323B-A837-84628B172F21> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x7fff90d2a000 - 0x7fff90d6afe7 libGLImage.dylib (??? - ???) <11B7E8A0-F475-32BD-9234-1E245384F586> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dyl ib
0x7fff90db4000 - 0x7fff90dcaff7 com.apple.ImageCapture (7.0.1 - 7.0.1) <BF4EC1CC-C998-3529-A69F-765774C66A6F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture. framework/Versions/A/ImageCapture
0x7fff90dcb000 - 0x7fff90dd8fff com.apple.CrashReporterSupport (10.7.4 - 352) <C806C4A3-25FE-3D62-BFF4-0DB41589CF83> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/Cra shReporterSupport
0x7fff90dd9000 - 0x7fff90f40fff com.apple.CFNetwork (520.4.3 - 520.4.3) <31D7A595-375E-341A-8E97-21E73CC62E4A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
0x7fff90f80000 - 0x7fff90f84ff7 com.apple.CommonPanels (1.2.5 - 94) <CA9C910D-E406-33E7-B8EE-C86EAA62AB68> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels. framework/Versions/A/CommonPanels
0x7fff90f85000 - 0x7fff90f85fff com.apple.CoreServices (53 - 53) <97E086D0-20B4-3BB4-BEE2-04EE5700D55B> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x7fff910cf000 - 0x7fff912a3ff7 com.apple.CoreFoundation (6.7.2 - 635.21) <62A3402E-A4E7-391F-AD20-1EF20236CE1B> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff912a4000 - 0x7fff912b3fff libxar.1.dylib (??? - ???) <58B07AA0-BC12-36E3-94FC-C252719A1BDF> /usr/lib/libxar.1.dylib
0x7fff912b4000 - 0x7fff912b4fff com.apple.audio.units.AudioUnit (1.7.2 - 1.7.2) <04C10813-CCE5-3333-8C72-E8E35E417B3B> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x7fff914af000 - 0x7fff91593ed7 libobjc.A.dylib (228.0.0 - compatibility 1.0.0) <76082BBC-446B-3355-AED5-0DBCEE600CB2> /usr/lib/libobjc.A.dylib
0x7fff91594000 - 0x7fff915f0ff7 com.apple.HIServices (1.21 - ???) <25FBDEA4-871F-3A58-A525-0E1799945522> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices
0x7fff91918000 - 0x7fff91918fff com.apple.ApplicationServices (41 - 41) <E23F1CED-C0FB-35A8-9657-484C5E6A32AE> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
0x7fff91919000 - 0x7fff91994ff7 com.apple.print.framework.PrintCore (7.1 - 366.3) <51681D6E-62D3-3B7D-9981-D3FC3568BAB6> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ PrintCore.framework/Versions/A/PrintCore
0x7fff91995000 - 0x7fff91a18fef com.apple.Metadata (10.7.0 - 627.35) <6769AD6A-58D2-3D25-B289-15C65B82CF8D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
0x7fff92004000 - 0x7fff92028fff com.apple.RemoteViewServices (1.4 - 44.1) <EA3837DF-A3A3-37FF-AE11-D50048D5F21A> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/Remot eViewServices
0x7fff9202e000 - 0x7fff92070fff com.apple.corelocation (330.12 - 330.12) <61E65321-958C-3E89-9F02-05BD2B7D898D> /System/Library/Frameworks/CoreLocation.framework/Versions/A/CoreLocation
0x7fff9209f000 - 0x7fff920a3fff libmathCommon.A.dylib (2026.0.0 - compatibility 1.0.0) <FF83AFF7-42B2-306E-90AF-D539C51A4542> /usr/lib/system/libmathCommon.A.dylib
0x7fff920a4000 - 0x7fff920edff7 com.apple.framework.CoreWLAN (2.1.2 - 212.2) <F8F7E96C-C256-329B-AAEE-3F770B79EE04> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN
0x7fff9212a000 - 0x7fff92207fef libsystem_c.dylib (763.13.0 - compatibility 1.0.0) <535C622E-2C14-3DD4-98D0-EA181DF8D582> /usr/lib/system/libsystem_c.dylib
0x7fff9270c000 - 0x7fff927adff7 com.apple.LaunchServices (480.34 - 480.34) <67D5B865-B4B6-3522-8652-654A4E3F4B6D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 3
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 1311
thread_create: 2
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=186.8M resident=130.5M(70%) swapped_out_or_unallocated=56.4M(30%)
Writable regions: Total=1.1G written=4280K(0%) resident=5508K(0%) swapped_out=0K(0%) unallocated=1.1G(100%)
REGION TYPE VIRTUAL
=========== =======
CG shared images 96K
CoreServices 1304K
JS JIT generated code 8K
JS JIT generated code (reserved) 1.0G reserved VM address space (unallocated)
MALLOC 44.2M
MALLOC guard page 64K
SQLite page cache 288K
STACK GUARD 56.0M
Stack 10.5M
VM_ALLOCATE 64K
__CI_BITMAP 80K
__DATA 17.4M
__IMAGE 528K
__LINKEDIT 61.0M
__RC_CAMERAS 248K
__TEXT 125.9M
__UNICODE 544K
mapped file 24.7M
shared memory 312K
=========== =======
TOTAL 1.3G
TOTAL, minus reserved VM space 343.2M
Model: MacBookPro9,1, BootROM MBP91.00D3.B06, 4 processors, Intel Core i7, 2.6 GHz, 8 GB, SMC 2.1f170
Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In, 512 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333531533643465238432D50422020
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333531533643465238432D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF5), Broadcom BCM43xx 1.0 (5.106.198.19.21)
Bluetooth: Version 4.0.7f2, 2 service, 11 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: APPLE HDD HTS727575A9E362, 750.16 GB
Serial ATA Device: HL-DT-ST DVDRW GS31N
USB Device: hub_device, 0x8087 (Intel Corporation), 0x0024, 0x1a100000 / 2
USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0x1a110000 / 3
USB Device: hub_device, 0x8087 (Intel Corporation), 0x0024, 0x1d100000 / 2
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0x1d180000 / 3
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x1d182000 / 6
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0252, 0x1d183000 / 5
USB Device: BRCM20702 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x1d181000 / 4
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821d, 0x1d181300 / 7sBack up all data.
In the Finder, select Go ▹ Go to Folder from the menu bar, copy the text on the line below into the box that opens, and press return:
/System/Library/StagedFrameworks/Safari/WebKit.framework
A Finder window will open with an item selected. Move the selected item, WebKit.framework, to the Desktop. You may be prompted for your login password.
Run Software Update. If a Safari update is available, install it. Test.
If no Safari update appears in Software Update, put back the item you moved to the Desktop, then launch Disk Utility and repair permissions. Post your results. -
Dual monitor use audio output for movie and other for MBP
is it possible im watching a movie on one and wated to answer factime call or watch youtube on my mbp and just screamed out my tv speakers.....i want fual monitoring but separate audio any help?
Other alternatives include
I know on mackbooks I've seen firewire used as an input for a Weiss Dac if you're into two channel audio. Do any reiceivers take firewire as an input for hometheater? Has anyone tested Firewire outputs on their W series? I'm told that firewire is sometimes preferable to USB, I'm not sure why this would be, can USB support passthrough of DTS encoded signals?
In the case that firewire works and you Do not have a firewire source, maybe something like this would be of value It converts firewire to digital coaxial s/pdif and allows passthrough of DTS and AC3.
http://www.m-audio.com/images/global/manuals/FireWire-Audiophile_Manual.pdf
As I'm into audio the critical thing here (and what you're paying for when you purchase blue-ray, is maintaining the digital information from the disk in an unconverted form. You want a direct bit pass through, and you want as little jitter introduced to the signal as possible. You most certainly don't want the sound card getting in the way, Digtital to Analog converting and then reverse packaging it up and putting it out over the soundcard digital out. My problem is I'm not familiar enough with computer audio to know how exactly the sounds is transmitted from your blue ray drive to the digital interface you've chosen.
Anyone know why USB digital out would not be a prefered method?
Moderator note; comment removed which contravened forum rules -
Can't boot MBP. New HDD worked for a day, back at square one
Out of no-where my MBP froze after bring it out of sleep mode. I held down the power button and when turning it on it stuck at the grey spinning circle screen. I tried:
1) reset PRAM
2) booting to recovery partition and repair permissions and disk.Disk repair failed, can't recall the exact error.
3) booting to 10.7 CD that I made from my Lion AppStore download and repairing permissions and disk. Disk repair failed, can't recall the exact error.
I had a spare drive lying around so I opened it up and replaced the drive. Booted to the Lion DVD, formatted the drive and install Lion. Everything installed no problems. After the install I downloaded all of my applications and starting restoring all of my data from a backup drive. After getting almost all of my things set up to my liking the machine hung. I held down the power button and then pressed power again to turn on the machine. After the Apple logo screen the dreaded flashing question mark came onto the screen.
I can take either of these two HDDs and place them into an enclosure and read/write data on the disk without a problem so it seems unlikely that I had two bad (flaky) HDDs. I tried inserting my 10.6 and 10.5 install discs and holding D before the grey screen to start the hardware diagnostics tool but it just boots onto a black screen with a white cursor in the top left corner. I'm afraid to let it sit at this screen too long because the machine gets pretty hot near the display hinge.
Any ideas?I tried that earlier but I guess I didn't wait long enough. I wasn't factoring in that the load time would be slower booting it via USB. If it's just that cable that would be great. It's ironic if that's the problem because I replaced that cable 6-8 months ago because my sleep indicator stopped working. I may have the old one, if not I'll order one since it's only a $30-40 part and let you know if that resolved it.
-
Problem: DVD-RAM can no longer be read on MBP C2D
The "MATSHITA DVD-R UJ-857D" in my MacBook Pro C2D is said to have read (but not write) support for DVD-RAM media.
During the first few weeks of its lifetime, reading DVD-RAMs definitely worked. But now, no more, no matter what brand of media I try.
All other types of optical media continue to work as advertised (read and write).
I wonder whether this is a physical defect (but then why doesn't it affect other types of media?) or an issue caused by recent sopftware updates (but when I boot from an external DVD-drive using the very original MacOS DVD with no updates at all, why do I still not get read support on the internal drive?).
AFAIK there has not been any recent firmware update for this model. So what can be the reason? Should I let Apple swap the drive? Has anyone else observed the same issue?
Guido
MBP C2D Mac OS X (10.4.8) MATSHITA DVD-R UJ-857DHey Grant,
thought you'd like to know my "cleaning the lens with a cloth" worked fine - uh... but for about three days only, then back to the same old, same old.
I'd originally slid a business card covered with a lens cleaning cloth (from my camera bag) to clean the lens, and although the cloth emerged mostly pristine, I figured it must've done the trick as the drive started working again.
So this time, I decided to go in deeper. I actually took the whole drive apart - case off, drive out, drive dismantled - and I had a long look around to see if any parts looked dirty or damaged...
I found just one thing - the small silver rod on which the read/write head travels (the servomechanism that moves up and down the disc radius as it reads/writes) had some 'oily gunk' at the point where the travelling-head's 'sleeve' met it - when I tried to move the head manually up and down the rod, it sort of staggered along. So I cleaned off the gunk with a cotton bud and then slid the drive-head up and down a few times 'till it seemed to run freely.
Put everything back - and fired up my Mac Pro. And the drive has been 100% fine since then - two whole weeks!
Maybe this time I've cracked it? (for my drive at least)
Roger -
Time Capsule - can no longer access on MBP Leopard
For the past 6 or 7 weeks I can no longer access my Time Capsule from my MBP Leopard. However, I do not beleive this is a Time Capsule issue as I am still accessing (and backing up) successfully from a MBP running Snow Leopard. Note, the access and backup were running fine for over a year and suddenly just stopped working. I've done the basics like repair permissions, software update, checked everything. For soem reason, when I try to access, I can see the Time Capsule, I can connect until I get to Data then "mylaptop Sparse Bundle". When I choose that disk image backup - just continues for ever and ever with a dialog box that says "trying to connect" or something like that.
Any ideas appreciated ...
thankslumiere wrote:
"the current volume could not be mounted". Also "The Current Time Machine backup disk can;t be found".
Has this Mac had any problems since the last successful backup? Such as hardware repairs, especially a new logic board? A full restore?
Is the +sparse bundle+ currently mounted? If so, eject it and try again.
If not, or if that doesn't help, try a "full reset" of Time Machine, per #A4 of Troubleshooting.
Interesting to note that the final backup (7 weeks ago) failed - it looked like hourly backups worked and the final one failed ("says in progress" ?)
Yes, that's the partial, failed backup. Since it's incomplete, it won't appear in the "Star Wars" display, etc. Once Time Machine gets started, it will "recover" it, and convert it into a normal backup, with a new date & Time.
After that long without a backup, Time Machine will have a lot of work to do (including recovering the partial backup), so connect via Ethernet if at all possible. It will still take a while, but be 2-3 times faster than WIFI. -
Choosing a PXIe controller for streaming 200 MBps
Warning: This is a long post with several questions. My appologies in advance.
I am a physics professor at a small liberal-arts college, and will be replacing a very old multi-channel analyzer for doing basic gamma-ray spectroscopy. I would like to get a complete PXI system for maximum flexability. Hopefully this configuration could be used for a lot of other experiments such as pulsed NMR. But the most demanding role of the equipment would be gamma-ray spectroscopy, so I'll focus on that.
For this, I will need to be measuring either the maximum height of an electrical pulse, or (more often) the integrated voltage of the pulse. Pulses are typically 500 ns wide (at half maximum), and between roughly 2-200 mV without a preamp and up to 10V after the preamp. With the PXI-5122 I don't think I'll need a preamp (better timing information and simpler pedagogy). A 100 MHz sampling rate would give me at least 50 samples over the main portion of the peak, and about 300 samples over the entire range of integration. This should be plenty if not a bit of overkill.
My main questions are related to finding a long-term solution, and keeping up with the high data rate. I'm mostly convinced that I want the NI PXIe-5122 digitizer board, and the cheapest (8-slot) PXIe chassis. But I don't know what controller to use, or software environment (LabView / LabWindows / homebrew C++). This system will likely run about $15,000, which is more than my department's yearly budget. I have special funds to accomplish this now, but I want to minimize any future expenses in maintenance and updates.
The pulses to be measured arrive at random intervals, so performance will be best when I can still measure the heights or areas of pulses arriving in short succession. Obviously if two pulses overlap, I have to get clever and probably ignore them both. But I want to minimize dead time - the time after one pulse arrives that I become receptive to the next one. Dead times of less than 2 or 3 microseconds would be nice.
I can imagine two general approaches. One is to trigger on a pulse and have about a 3 us (or longer) readout window. There could be a little bit of pileup inspection to tell if I happen to be seeing the beginning of a second pulse after the one responsible for the trigger. Then I probably have to wait for some kind of re-arming time of the digitizer before it's ready to trigger on another pulse. Hopefully this time is short, 1 or 2 us. Is it? I don't see this in the spec sheet unless it's equivalent to minimum holdoff (2 us). For experiments with low rates of pulses, this seems like the easiest approach.
The other possibility is to stream data to the host computer, and somehow process the data as it rolls in. For high rate experiments, this would be a better mode of operation if the computer can keep up. For several minutes of continuous data collection, I cannot rely on buffering the entire sample in memory. I could stream to a RAID, but it's too expensive and I want to get feedback in real time as pulses are collected.
With this in mind, what would you recommend for a controller? The three choices that seem most reasonable to me are getting an embedded controller running Windows (or Linux?), an embedded controller running Labview real-time OS, or a fast interface card like the PCIe8371 and a powerful desktop PC. If all options are workable, which one would give me the lowest cost of upgrades over the next decade or so? I like the idea of a real-time embedded controller because I believe any run-of-the-mill desktop PC (whatever IT gives us) could connect and run the user interface including data display and higher-level analysis. Is that correct? But I am unsure of the life-span of an embedded controller, and am a little wary of the increased cost and need for periodic updates. How are real-time OS upgrades handled? Are they necessary? Real-time sounds nice and all that, but in reality I do not need to process the data stream in a real-time environment. It's just the computer and the digitizer board (not a control system), and both should buffer data very nicely. Is there a raw performance difference between the two OSes available for embedded controllers?
As for live processing of the streaming data, is this even possible? I'm not thinking very precisely about this (would really have to just try and find out), but it seems like it could possibly work on a a 2 GHz dual-core system. It would have to handle 200 MBps, but the data processing is extremely simple. For example one thread could mark the beginnings and ends of pulses, and do simple pile-up inspection. Another thread could integrate the pulses (no curve fitting or interpolation necessary, just simple addition) and store results in a table or list. Naievely, I'd have not quite 20 clock cycles per sample. It would be tight. Maybe just getting the data into the CPU cache is prohibitively slow. I'm not really even knowledgeable enough to make a reasonable guess. If it were possible, I would imagine that I would need to code it in LabWindows CVI and not LabView. That's not a big problem, but does anyone else have a good read on this? I have experience with C/C++, and some with LabView, but not LabWindows (yet).
What are my options if this system doesn't work out? The return policy is somewhat unfriendly, as 30 days may pass quickly as I struggle with the system while teaching full time. I'll have some student help and eventually a few long days over the summer. An alternative system could be built around XIA's Pixie-4 digitizer, which should mostly just work out of the box. I prefer somewhat the NI PXI-5122 solution because it's cheaper, better performance, has much more flexability, and suffers less from vendor lock-in. XIA's software is proprietary and very costly. If support ends or XIA gets bought out, I could be left with yet another legacy system. Bad.
The Pixie-4 does the peak detection and integration in hardware (FPGAs I think) so computing requirements are minimal. But again I prefer the flexibility of the NI digitizers. I would, however, be very interested if data from something as fast as the 5122 could be streamed into an FPGA-based DSP module. I haven't been able to find such a module yet. Any suggestions?
Otherwise, am I on the right track in general on this kind of system, or badly mistaken about some issue? Just want some reassurance before taking the plunge.drnikitin,
The reason you did not find the spec for the rearm time for
the 5133 is because the USB-5133 is not capable of multi-record acquisition. The rearm time is a spec for the reference
trigger, and that trigger is used when fetching the next record. So every time you want to do another fetch
you will have to stop and restart your task.
To grab a lot of data increase your minimum record size. Keep in mind that you have 4MB of on board
memory per channel.
Since you will only be able to fetch 1 record at a time,
there really isn’t a way to use streaming.
When you call fetch, it will transfer the amount of data you specify to
PC memory through the USB port (up to 12 MB/s for USB 2.0 – Idealy).
Topher C,
We do have a Digitizer that has onboard signal processing
(OSP), which would be quicker than performing post processing. It is
the NI 5142
and can perform the following signal
processing functions. It is
essentially a 5122 but with built in OSP.
It may be a little out of your price range, but it may be worth a
look.
For more
information on streaming take a look at these two links (if you havn’t
already).
High-Speed
Data Streaming: Programming and Benchmarks
Streaming Options for PXI
Express
When dealing with different LabVIEW versions
it is important to note that previous versions will be compatible with new
versions; such as going from 8.0 to 8.5.
Keep in mind that if you go too far back then LabVIEW may complain, but
you still may be able to run your VI. If
you have a newer version going to an older version then we do have options in
LabVIEW to save your VI for older versions.
It’s usually just 1 version back, but in LabVIEW 8.5 you can save for
LabVIEW 8.2 and 8.0.
ESD,
Here is the link
I was referring to earlier about DMA transfers. DMA is actually done every time you call a
fetch or read function in LabVIEW or CVI (through NI-SCOPE).
Topher C and ESD,
LabVIEW is a combination of a compiled
language and an interpreted language.
Whenever you make a change to the block diagram LabVIEW compiles
itself. This way when you hit run, it is
ready to execute. During execution LabVIEW
uses the run-time engine to reference shared libraries (such as dll’s). Take a look at this DevZone article about
how LabVIEW compiles it’s block diagram (user code).
I hope all of this information helps!
Ryan N
National Instruments
Application Engineer
ni.com/support
Maybe you are looking for
-
Reverse Charge up of budget again during settlement from project AUC to FA
With investment profile, Charging up of budget during settlement from project AUC to FA is done, In order to reverse the budger consumption, is it possible to reverse by FB08 for the AUC to FA posting Or it must be done through adjustment? Please inc
-
Can no longer send pictures in text that I once did. "Unsupported file type"
The other day my phone began saying I could not longer send pictures in MMS. Pictures I sent the previous week are now an unsupport file type. They are .jpg and .pngs. I have to take a screenshot of them all now, crop out the excess stuff, and then
-
[Solved] Recommend a package with pacman for "Command Not Found"
Is there a way to get Pacman to recommend a package name like in ubuntu, for example: If I were to type in a terminal ifconfig and it said "Command not found" Could Pacman recommend the package net-tools? Last edited by jack9099 (2011-08-03 14:33:39)
-
"location" method in "windows" object
Hi, I have the following prob: on the app. that I'm trying to capture (with captivate 3.x), I'm using the javascript: window.location (the method "location" on the object "windows") to open a popup with content inside. It works well of course without
-
How to truncate a partition in owb
I wonder how can i achieve truncating a partition before loading into this target table. I found this pre-mapping prcess where we have this option of truncating a table, but how can i just truncate a partition within a table in a mapping? please advi