Aperture on MBpro
I have a macbookpro with a 300 gig hardrive and three gigs of ram. I have about 150 gigs of free space on the drive. I like iphoto but would like some of the features of Aperture especially now that I have a new digital slr. Anyway, I am worried that my mbpro will slow to a crawl with Aperture. Currently under iphoto I have to wait about 10 to 15 seconds each time I save edits to a photo i.e., hit 'Done'. Will Aperture be faster? Also, should I download the free version and then buy it online? Are there disadvantages of doing it this way? Should I go with managed or referenced master with a macbookpro? thanks in advance. Please try to answer all the questions.
scubanut wrote:
I have a macbookpro with a 300 gig hardrive and three gigs of ram. I have about 150 gigs of free space on the drive. I like iphoto but would like some of the features of Aperture especially now that I have a new digital slr. Anyway, I am worried that my mbpro will slow to a crawl with Aperture.
Welcome to Aperture!
Properly run Aperture runs well for a laptop on a MBP with 3 GB RAM; however do be aware that Aperture is a hardware hog that likes strongest possible hardware, and images handling can involve slowdowns depending on workflow and Aperture setup.
Pretty much everything impacts AP performance, so the more things you optimize the better. The maximum RAM of MBPs, although quite workable, will always be limiting. Good policy is to restart or at least close as many irrelevant applications as necessary prior to an extended Aperture work session.
Steve Weller, builder of the excellent <http://www.bagelturf.com/index.html> Aperture website, discusses speed improvements here:
<http://discussions.apple.com/thread.jspa?threadID=1273934&tstart=75>
If you ever do run into performance issues, work to dial in on each of the performance tweaks he discusses.
Currently under iphoto I have to wait about 10 to 15 seconds each time I save edits to a photo i.e., hit 'Done'. Will Aperture be faster?
Each workflow and setup is different, so you will have to do your own tests.
Also, should I download the free version and then buy it online? Are there disadvantages of doing it this way?
IMO it does not really matter. Max the RAM in your MBP if it is not already, buy the Luna/Long Aperture 2 tutorial CD/book, bring your OS to 10.4.11, then do the trial. I strongly recommend that every digital photog with adequate computer hardware first spend $33 and work through the tutorial CD Apple Pro Training Series: Aperture 2 (Apple Pro Training Series) by Ben Long, Richard Harrington, and Orlando Luna (Paperback - May 8, 2008), Amazon.com.
I just received the new v2 tutorial and am just now reviewing it, but the earlier version was excellent. Note that the value is in the tutorial, not in using the book as a manual. The time spent learning modern digital image capture workflow via the tutorial is invaluable.
IMO a cursory examination of Aperture usually turns out to be mostly a waste of time, or leads to bad workflow habits or folks simply do not get it. Carefully working the tutorial is by far the best way to learn this new killer app category.
Should I go with managed or referenced master with a macbookpro?
On a laptop you do want to manage by Referencing image Masters. Hard drives slow as they fill, so at some point - perhaps immediately - you will want your Masters on one or more external Firewire 800 hard drives. Your half-full internal hard drive is already slowing down, and DSLR capture can add images very quickly. OWC <http://www.owcomputing.com/> "Mercury to go" FW800/USB2 drives are a good external solution if you need portable.
With Referenced Masters, simply Finder-copy each batch of images to the external hard drive and eject the camera card. Then (after backup of images) from within Aperture Import the images by Reference (when you go to import, on the right hand side of the import window select "Store files in their current location").
A good rule of thumb is not to fill any drive more than 70%, and for best speed keep important drives no more than 50% full.
Good luck! IMO Aperture is must-have for DSLR photogs with adequate computer hardware like yours.
-Allen Wicks
Similar Messages
-
Can iCloud be used to synchronize a very large Aperture library across machines effectively?
Just purchased a new 27" iMac (3.5 GHz i7 with 8 GB and 3 TB fusion drive) for my home office to provide support. Use a 15" MBPro (Retina) 90% of the time. Have a number of Aperture libraries/files varying from 10 to 70 GB that are rapidly growing. Have copied them to the iMac using a Thunderbolt cable starting the MBP in target mode.
While this works I can see problems keeping the files in sync. Thought briefly of putting the files in DropBox but when I tried that with a small test file the load time was unacceptable so I can imagine it really wouldn't be practical when the files get north of 100 GB. What about iCloud? Doesn't appear a way to do this but wonder if that's an option.
What are the rest of you doing when you need access to very large files across multiple machines?
David VoranHi David,
dvoran wrote:
Don't you have similar issues when the libraries exceed several thousand images? If not what's your secret to image management.
No, I don't .
It's an open secret: database maintenance requires steady application of naming conventions, tagging, and backing-up. With the digitization of records, losing records by mis-filing is no longer possible. But proper, consistent labeling is all the more important, because every database functions as its own index -- and is only as useful as the index is uniform and holds content that is meaningful.
I use one, single, personal Library. It is my master index of every digital photo I've recorded.
I import every shoot into its own Project.
I name my Projects with a verbal identifier, a date, and a location.
I apply a metadata pre-set to all the files I import. This metadata includes my contact inf. and my copyright.
I re-name all the files I import. The file name includes the date, the Project's verbal identifier and location, and the original file name given by the camera that recorded the data.
I assign a location to all the Images in each Project (easy, since "Project" = shoot; I just use the "Assign Location" button on the Project Inf. dialog).
I _always_ apply a keyword specifying the genre of the picture. The genres I use are "Still-life; Portrait; Family; Friends; People; Rural; Urban; Birds; Insects; Flowers; Flora (not Flowers); Fauna; Test Shots; and Misc." I give myself ready access to these by assigning them to a Keyword Button Set, which shows in the Control Bar.
That's the core part. Should be "do-able". (Search the forum for my naming conventions, if interested.) Or course, there is much more, but the above should allow you to find most of your Images (you have assigned when, where, why, and what genre to every Image). The additional steps include using Color Labels, Project Descriptions, keywords, and a meaningful Folder structure. NB: set up your Library to help YOU. For example, I don't sell stock images, and so I have no need for anyone else's keyword list. I created my own, and use the keywords that I think I will think of when I am searching for an Image.
One thing I found very helpful was separating my "input and storage" structure from my "output" structure. All digicam files get put in Projects by shoot, and stay there. I use Folders and Albums to group my outputs. This works for me because my outputs come from many inputs (my inputs and outputs have a many-to-many relationship). What works for you will depend on what you do with the picture data you record with your cameras. (Note that "Project" is a misleading term for the core storage group in Aperture. In my system they are shoots, and all my Images are stored by shoot. For each output project I have (small "p"), I create a Folder in Aperture, and put Albums, populated with the Images I need, in the Folder. When these projects are done, I move the whole Folder into another Folder, called "Completed".)
Sorry to be windy. I don't have time right now for concision.
HTH,
--Kirby. -
Aperture not seeing images in camera
I have two copies of Aperture: one on my MBPro and one on a recently acquired iMac 2.4GHz.
Aperture on the iMac does not see the images on the camera, although recognises that the camera has been attached. The images are visible in iPhoto.
On the MBP, Aperture sees the images on the memory card of my Nikon D70 and imports without problem.
Any ideas why (or what I have missed) this might be happening. The two copies of Aperture are not running at the same time.I actually do have one but I wanted to try without. When I later tried with the card reader (that was after having the version on the MBP recognise and import the images) nothing happened at first, although it identified the card as a Nikon D70s; but when I tried the Import icon, that worked. A bit less smooth than I was expecting.
-
Aperture - library management and external HDD question
Hi all.
I have just graduated from a point and shoot to a Panasonic GH2 (love it), and have now begun using Aperture 3 rather than iPhoto on my early 2008 MB Pro to manage my photos going forwards. Of course, I’ve now discovered that Aperture is quite the resource hog and so it’s upgrade time (darn, “have” to buy a new ‘puter!). I have a 2011 MB Pro (2.3Ghz i7 with 512GB SSD) on order and 8GB of DDR 3 arriving from Crucial. Since I have this brand-new-computer opportunity I want to make sure I’m organising things properly before I start transferring things across, and so have a few Aperture-related questions. (In case it’s relevant, I’m shooting in RAW+JPEG. So far I’ve been using RAW as master, but have since learnt it might be a good idea to import JPG as master and switch to RAW only when I need to make corrections, so I’ll probably do that going forwards.)
I understand that moving to referenced masters on an external drive might be a good idea and save me precious SSD-space. To that end, questions are:
1. Can anyone recommend a companion external HDD for Aperture and the 2011 MBPro? I guess either FW800 or Thunderbolt are the way to go. The Lacie Little Big Disk Thunderbolt might be an option but is this overkill for Aperture masters or would FW800 be sufficient. I’ve also seen the G-Tech G-RAID mini, Lacie Rugged – thoughts welcome.
Key requirements are a) as compact as possible, and b) bus powered.
2. What kind of performance can I expect if I go down this route? Is there going to be significant loading/processing delay whenever I switch to a new image?
3. How will Aperture cope with (eg) syncing photos to iPad / iPhone if the drive containing the masters isn’t connected? Put another way, are JPG renders saved in the Aperture library (i.e. on my MBP SSD) or with the masters?
Thanks in advance to anyone who responds!
AljrobAljrob_UK wrote:
...I have a 2011 MB Pro (2.3Ghz i7 with 512GB SSD) on order and 8GB of DDR 3 arriving
...I understand that moving to referenced masters on an external drive might be a good idea and save me precious SSD-space.
1. Can anyone recommend a companion external HDD for Aperture and the 2011 MBPro? I guess either FW800 or Thunderbolt are the way to go.
...Key requirements are a) as compact as possible, and b) bus powered.
OWC (an excellent vendor) has the Elite Pro Mini hard drive that meets your specs:
http://eshop.macsales.com/shop/firewire/EliteALmini/eSATA_FW800_FW400_USB
Thiunderbolt drives are not mainstream yet but eSATA and FW800 both work well. The multiple connection methods of OWC drives allow very desirable flexibility when purposing/repurposing drives.
Note too that the MBP optical drive can be replaced with up to a 1-TB hard drive DIY or OWC will do it for you. That is what I am doing with my 17" 2011 MBP.
2. Is there going to be significant loading/processing delay whenever I switch to a new image?
SSD latency is orders of magnitude less than hard drives. Switching to a new image even fast hard drives with fast connectivity add significant latency delay. To avoid that what I do is leave (Referenced) Masters on the SSD until all editing is complete (which may be a few weeks). Only then do I use Aperture to change the Referenced Masters location from the SSD to a large external drive.
What kind of performance can I expect if I go down this route?
With Masters on the SSD and 8 GB RAM imports/exports are very fast and all Aperture editing is essentially instant. You will be pleased!
Suggested workflow steps for Referenced Masters:
• Use a FW card reader or MBP slot to copy to a file folder on the SSD (never directly into Aperture or any other images management app). With fast camera cards copy times are quick, but cheap slow cards can slow this step down a lot.
• Eject and physically disconnect the card reader.
• Back up that file folder on external drive(s).
• Only after backup is complete, reformat the camera card in-camera.
• Import images into Aperture from the file folder on the SSD.
HTH
-Allen Wicks -
I installed Aperture 3 and the GPS scanning worked fine but I am having trouble with Faces. It shows a progress bar and only about 5% after 5 hours. I let the computer run overnight but this morning my MBpro wouldn't wake up. What should I do? Could it take more than 5 or 6 mins to wake up? It didn't sound busy (no HD noise). I have about 20k images (130gb worth)
The Library file page in the User Manual is a good place to start:
Working with Library Files
Aperture lets you select Images and/or Projects, and export them as a Library. You can then either use this Library, or import it into another Library. When you import, you are given the option to either merge (useful if you have exported from the Library into which you are importing) or copy.
In general, it is advised that you put as many files in one Library as possible. The standard exceptions are multiple photographers not working for the same company, images that need to be sequestered for legal reasons, and special collects that are not based on a single photographer (mainly scanned archives, but ****, too). The reason for keeping your Library big is that the Library is an index of everything in it. The more that's in it, the easier it is to find.
If the number of Images that you don't want to ever have show up when you use Faces is not large, just delete the Faces Position Box from them. This can be done by clicking the "x" if the box is showing, or right-clicking a proposed Face and selecting "Not a face". -
Aperture 3.03 For me preview generation performance is now even slower!
Set up:
24" iMac, Intel Core 2 Duo 2.8Ghz, 4Gb RAM, Radeon HD2600 with 256Mb, 1Tb 7200 Seagate Barracuda HD.
Aperture 3.03, RAW 3.02
OSX 10.6.3
With a Canon 5D Mark II RAW photo (25Mb or so) with some simple adjustments generating a preview is now taking 1 minute per photo. Which is even slower than version 3.02.
I have the previews full size and on quality 8.
Does anyone with the 5D see faster performance on preview of this size, on this sort of Mac?
I want to try and find out if this is normal performance or not before going through all the things I tried in 3.02 which had no effect (clearing caches, rebuilding library, rebuilding thumbnails, de-fragging by copying library to another drive and back, deleting preference files).
I've also had the problem with 3.03 where faces get rotated 90 degrees, so not too impressed so far with this version.Same here. Previews at 1680x1680 (the max rez of my 20" iMac screen), quality 8, and they take about 2 secs each on the iMac spec'd in my sig. Same on my MBPro, though those are constrained to 1440x max.
Are you talking about just generating a standard preview, or a 100% view render, or what?
I know (still even with 3.0.3) it takes a LONG time to render a 100% view of a photo if it has a bunch of adjustments on it (highlight/shadows + edge sharpen) are the worst for this)... But it does seem a bit faster doing this task now, than with 3.0.2... -
Advice on New Computer for Aperture
I was hoping to get some advice...I have been using Aperture for a few years. Now using v3. I currently have a MBpro and an Imac-both 3 years old. I use 3 managed Aperture libraries - one that has all my travel, one for local work and one for an organization I work with. I just do better with 3 than one large. Right now I am at about 700GB and all 3 reside on a Rugged 1T drive. I backup to a 3T drive and another 1T. So 3 copies in all...(A 4th copy for the 2 personal libs) I am not using Vaults. I do use Time Machine.
I do a lot of casual work in the living room on the MBP and I also use it when I travel or go out in the city. I do more serious editing on the 21" iMac. I move the Rugged between the laptop and iMac but it is now making me nervous as it disconnects too easily. I happen to be looking to upgrade my computer and am thinking of going to a one computer set up. A Retina 13" (which would be great for travel) and a desktop setup with a 27" monitor and keyborad etc. I will not be able to keep all the libaries on the laptop-(even if I max out with the 700GM flash memory, which is an expensive option.) But with 500 I could keep 2 on there. So, I would need to buy another portable drive if I want to continue to work in two places with access to all 3. Likely a Thunderbolt 2T if that exisists. At least with one computer I would not have to keep mounting and umounting the external drive-which seems to be causing issues. I am often getting Aperture messages for inconsistanceis - directly related to the Rugged drive unmounting by accident. I understnad my issue may be directly related to this particular Rugged drive/and or cable. It never has issues on the iMac-only the MB pro.
Can anyone speak to working between two locations and having to keep libraries on a portable drive? Aside from being nearly impossible to upgrade, is the Retina setup with an external Thurderbolt monitor a smart one? Obviously I lose the glory of the R diplay when I do this.
If there are other considerations for a 2 location setup, I am all ears.
Thanks!
NJI use both managed and reference libraries.
When I am working on a project between different computers, I maintain those on portable drives and they are managed libraries. I just move the drives between different computers and open the library. I could make them referenced.
Once I am done with the project, I import the library into my master library (I maintain a master library for each year), and once imported, I relocated my masters to a folder based system with a separate folder for each project. I do this because it is easier to get to the master picture outside of the Aperture Library. My current master libraries for the years 2011, 2012 and 2013 reside on an internal 2TB drive and I keep their size small by storing my referenced images on a Thunderbolt drive. BUT, my libraries from 2001-2009 are stored on firewire drive with the images stored as referenced images on other firewire drives.
At the start of each year I create a folder structure on an external drive for storing my referenced images. The top folder is the year called for example 2013 Pictures. Inside this folder I create a series of folders, one for each month of the year plus Miscellaneous plus Misc Libraries. I also add folders for things like the pictures I upload to Facebook, Photo.net, or the place I have things printed. Inside each month of the year folder, as I complete projects, I create a folder with the project date (YYMMDD) and relocate the master files for the project to this folder. This project folder can have subfolders, but I make sure it contains all of the working files related to the project.
Does this make any sense to you? -
I'm a avid iphoto user and have about 20+ gigs of photos on my MBpro. I don't presently own a camera that shoots raw but expect to buy one in the next year or two. A photographer is going to give us a thousand pics from our recent wedding weekend and I wanted to know whether I should ask for them in raw or jpeg. I know iphoto can import raw but is it worth it to buy Aperture to possibly edit the pics? I fiddle with the histogram settings in iphoto quite a bit.
Second question: is Aperture easy to administer? We are running out of room on our hardrive and will probably have to store some photos on an external drive. Is this complicated? Time Machine has nearly filled our 300gig external drive and so we will probably need to buy a larger external drive soon. Should I stick with iphoto or progress to Aperture?
Any advice would be great. thxBy all means get your wedding pix in RAW format. In fact the photog almost surely has the pix in RAW+JPEG, so he/she should be willing to deliver in both formats at no cost difference. In addition to allowing huge latitude in post-process editing, RAW captures contain more image data.
I strongly recommend that every digital photog with adequate computer hardware first spend $33 and work through the tutorial CD Apple Pro Training Series: Aperture 1.5 (Apple Pro Training) by Orlando Luna and Ben Long (Paperback - Oct 18, 2006). Have the CD and a MacIntel with minimum 2 GB RAM (preferably more) prior to ordering the Aperture trial so you don't waste time of the 30 day trial. Note that the value is in the tutorial, not in using the book as a manual.
IMO trying Aperture without the tutorial's guidance is a waste of time, leading to bad habits and/or just not getting it.
Note that you probably should ignore Shell's confusing post above; IMO Shell is just confused.
When you do go to buy a DSLR, note that there is always a delay from the time any brand new DSLR is introduced until various software supports the new model's RAW conversions. Different RAW converters variously show up sooner/later, and different RAW converters work better/worse with different models. E.g. Adobe's Nikon D300 conversions are out now but apparently do not do a very good job.
Typically the time frame is 1-3 months, so the very earliest adopters of new models may have to wait a month or two to convert their RAW images. All good DSLRs have a RAW+JPEG capture choice, however, so even the earliest adopters can manage images immediately.
Safely storing 20,000+ images using a laptop as a base is complicated. No way around that reality. Aperture provides several mechanisms (vaults, projects, etc.) that assist in the the process, and there are regularly threads here on the topic.
-Allen Wicks -
IPhoto browser is gray and empty in Aperture 3
Running Lion on 2.5 ghz i7 MBpro. Downloaded Aperture 3 and tried to transfer photos over from iPhoto 11. I can transfer the whole library, but when i try to open the iPhoto browser in Aperture, it's gray and empty. Apple says they are aware of this problem when upgrading from Aperture 2 to 3, but I installed a full version of Aperture 3
I have a similar problem, except I haven't even been able to import my iPhoto (iPhoto 7.1.5) library into Aperture (3.1.1) at all. Would love to see some advice; my purchase of Aperture was pretty much predicated on being able to import my photos!
-
Mackbook Pro + Aperture 3 + 1TB drive + Time Machine + Carbonite....work flow?
I have Carbonite On-Line back up running incremental (wifi to the cloud) backup in the background I just learned that I can nominate folders for it to ignore..
So... to prevent it grinding away needlessly using up resources, I was daydreaming I would import RAW files from my camera into to a "TEMP" folder that I would have Carbonite ignore
I am disciplined at sorting through shots directly after importing them..
Perhaps I can also get Time Machine to ignore that "TEMP" folder too? (Although hard drive storage is less of a worry...
This way I only back up 'keeper shots'?
Am I getting warm? Is this a valid workflow / back up regime?
I hear Aperture 3 has file management functions that are helpful.. But I am not up to speed with what they are...
Carbonite WONT back up attached drives - only the Laptop own drive.. And I want my 'keeper' library shots on two back up systems..
Am I missing a trick? Looking for do's and donts - pitfalls to avoid etc.. I want to set things up the right way from the beginning, I plan to migrate all my RAW operations from iPhoto / Elements set up on a MBAir to a new MBPro running Aperture 3 in about a week.
Suggestions please..
Thanks in advance!hammer58 wrote:
During the initial setup for TM, there was one screen that required username wd_backup and password admin. Later I changed the username for the TM folder to garyham58 and a personal password. That is the username and password I am looking for.
As I understand it, the original name and password were supplied by WD and stored on the NAS. Any changes would have been stored on the NAS. And resetting it would have to be done via the NAS.
I would think that there is some way to reset TM and start from scratch
I fear you may have already done part of that, inadvertently, since the folder shows no contents.
But it's not a password for the Time Machine application; it's the sharing of the WD disk, which is done by WD. When you back up with Time Machine to a simple external HD, there is no password for the drive. When you back up over a network to a Time Capsule, or a USB drive connected to it, you set up the password, if any, via Airport Utility, and I believe that's stored by the router as well as in the keychain on your Mac.
Do you still have the original 250 GB HD? If so, your best bet may be to get an enclosure for it, from http://www.macsales.com/ or the like. You can put the HD into it and connect it to your Mac via USB or FireWire, and it will become a normal external HD. Then you can start up from it and "clone" the HD to the new one.
Then you might be able to re-establish contact with the WD, and see your backups, unless they got erased during all the problems, or erase it and start over. -
Why does Aperture 3 suck so much? I'm not a troll...
I've been using Aperture 3 for 3 months now and I have downloaded the newest firmware update. I'm using a MacBook Pro with 4gb of RAM in it. And when I use Aperture 3 the only application I run alongside it is Safari. It hangs and crashes a lot. Especially when I'm using brushes. i brought my MBPro at Genius Bar (not-so Genius at all) at an Apple Retail Store here in Chicago, they did what they think is applicable to the problem yet to no avail it's still slow and crashes all the time. I now believe that if one is to use Aperture 3, they need a minimum of 8gb of RAM in their hardware. If not shy away from this software. This is a serious and legitimate criticism of this Apple product and look at forums everywhere, I'M NOT ALONE!!! APPLE WAKE UP, DO SOMETHING. APERTURE *****!!!
Crash Report once more:
Process: Aperture [403]
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Identifier: com.apple.Aperture
Version: 3.1.2 (3.1.2)
Build Info: Aperture-1530000~1
App Item ID: 408981426
App External ID: 3531551
Code Type: X86 (Native)
Parent Process: launchd [102]
Date/Time: 2011-04-25 21:00:52.561 -0500
OS Version: Mac OS X 10.6.7 (10J869)
Report Version: 6
Interval Since Last Report: 19827 sec
Crashes Since Last Report: 1
Per-App Interval Since Last Report: 30306 sec
Per-App Crashes Since Last Report: 1
Anonymous UUID: 410C2DDE-B37D-4BFE-9DAC-30D6C358371B
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 34
Thread 0: Dispatch queue: com.apple.main-thread
0 libSystem.B.dylib 0x96d0e09a mach_msg_trap + 10
1 libSystem.B.dylib 0x96d0e807 mach_msg + 68
2 com.apple.CoreFoundation 0x98d1b37f __CFRunLoopRun + 2079
3 com.apple.CoreFoundation 0x98d1a464 CFRunLoopRunSpecific + 452
4 com.apple.CoreFoundation 0x98d1a291 CFRunLoopRunInMode + 97
5 com.apple.HIToolbox 0x95deee04 RunCurrentEventLoopInMode + 392
6 com.apple.HIToolbox 0x95deebb9 ReceiveNextEventCommon + 354
7 com.apple.HIToolbox 0x95deea3e BlockUntilNextEventMatchingListInMode + 81
8 com.apple.AppKit 0x9631e78d _DPSNextEvent + 847
9 com.apple.AppKit 0x9631dfce -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156
10 com.apple.Aperture 0x004a5b18 0x1000 + 4868888
11 com.apple.AppKit 0x962e0247 -[NSApplication run] + 821
12 com.apple.prokit 0x00ccdfac NSProApplicationMain + 326
13 com.apple.Aperture 0x000049bd 0x1000 + 14781
14 com.apple.Aperture 0x00004799 0x1000 + 14233
Thread 1: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x96d34922 kevent + 10
1 libSystem.B.dylib 0x96d3503c _dispatch_mgr_invoke + 215
2 libSystem.B.dylib 0x96d344f9 _dispatch_queue_invoke + 163
3 libSystem.B.dylib 0x96d3429e _dispatch_worker_thread2 + 240
4 libSystem.B.dylib 0x96d33d21 _pthread_wqthread + 390
5 libSystem.B.dylib 0x96d33b66 start_wqthread + 30
Thread 2:
0 libSystem.B.dylib 0x96d0e0fa semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x96d3bc85 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x96d6aaa8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x916c4d48 -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x9167d9bd -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x9167d8a0 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0129507f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01293e60 -[XTThread run:] + 400
8 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
9 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
10 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
11 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 3:
0 libSystem.B.dylib 0x96d0e09a mach_msg_trap + 10
1 libSystem.B.dylib 0x96d0e807 mach_msg + 68
2 com.apple.framework.IOKit 0x97958c97 io_service_close + 97
3 com.apple.framework.IOKit 0x9790fb43 IOServiceClose + 32
4 com.apple.GeForceGLDriver 0x1696c063 gldDestroyContext + 51
5 GLEngine 0x167c7ddd gliDestroyContext + 144
6 com.apple.opengl 0x9796a97e CGLReleaseContext + 229
7 com.apple.QuartzCore 0x950bd10e fe_cgl_destroy_context + 34
8 com.apple.QuartzCore 0x950bbdcb accel_context_finalize + 138
9 com.apple.QuartzCore 0x95041b96 fe_release + 371
10 com.apple.QuartzCore 0x950bc179 fe_accel_purge + 141
11 com.apple.QuartzCore 0x950bf88f fe_context_purge + 97
12 com.apple.QuartzCore 0x950bfa08 fe_gl_finalize + 18
13 com.apple.QuartzCore 0x95041b96 fe_release + 371
14 com.apple.QuartzCore 0x9511261c -[CIOpenGLContextImpl invalidate] + 46
15 com.apple.QuartzCore 0x950af3a3 -[CIOpenGLContextImpl setOwner:] + 49
16 com.apple.QuartzCore 0x950bb721 -[CIContext invalidate] + 50
17 com.apple.QuartzCore 0x950bb6c3 -[CIContext dealloc] + 39
18 com.apple.geode 0x0106a6fd -[DGContextImpl dealloc] + 45
19 com.apple.geode 0x0108bfea -[DGOpenGLContext dealloc] + 79
20 com.apple.CoreFoundation 0x98ceaf38 CFRelease + 152
21 com.apple.CoreFoundation 0x98d03460 __CFBasicHashStandardCallback + 384
22 com.apple.CoreFoundation 0x98d0306e __CFBasicHashDrain + 478
23 com.apple.geode 0x0106a47d +[DGContextMgr _removeOldContexts:] + 761
24 com.apple.geode 0x0106a159 +[DGContextMgr cleanupContextHandler:] + 119
25 com.apple.proxtcore 0x012964e3 -[XTSubscription postMessage:] + 227
26 com.apple.proxtcore 0x0129611d -[XTList makeObjectsPerformSelector:withObject:] + 61
27 com.apple.proxtcore 0x01295b26 -[XTDistributor distributeMessage:] + 502
28 com.apple.proxtcore 0x01295761 -[XTThread handleMessage:] + 849
29 com.apple.proxtcore 0x0129a659 -[XTPortMsgQueue handleMachMessage:] + 185
30 com.apple.Foundation 0x916ea340 __NSFireMachPort + 388
31 com.apple.CoreFoundation 0x98d20772 __CFMachPortPerform + 338
32 com.apple.CoreFoundation 0x98d1c4db __CFRunLoopRun + 6523
33 com.apple.CoreFoundation 0x98d1a464 CFRunLoopRunSpecific + 452
34 com.apple.CoreFoundation 0x98d1a291 CFRunLoopRunInMode + 97
35 com.apple.Foundation 0x916c2640 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 279
36 com.apple.proxtcore 0x012962f5 -[XTRunLoopThread run:] + 453
37 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
38 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
39 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
40 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 4:
0 libSystem.B.dylib 0x96d0e09a mach_msg_trap + 10
1 libSystem.B.dylib 0x96d0e807 mach_msg + 68
2 com.apple.CoreFoundation 0x98d1b37f __CFRunLoopRun + 2079
3 com.apple.CoreFoundation 0x98d1a464 CFRunLoopRunSpecific + 452
4 com.apple.CoreFoundation 0x98d1a291 CFRunLoopRunInMode + 97
5 com.apple.Foundation 0x916c2640 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 279
6 com.apple.proxtcore 0x012962f5 -[XTRunLoopThread run:] + 453
7 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
8 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
9 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
10 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 5:
0 libSystem.B.dylib 0x96d0e0fa semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x96d3bc85 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x96d6aaa8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x916c4d48 -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x9167d9bd -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x9167d8a0 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0129507f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01293e60 -[XTThread run:] + 400
8 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
9 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
10 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
11 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 6:
0 libSystem.B.dylib 0x96d0e0fa semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x96d3bc85 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x96d6aaa8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x916c4d48 -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x9167d9bd -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x9167d8a0 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0129507f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01293e60 -[XTThread run:] + 400
8 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
9 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
10 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
11 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 7:
0 libSystem.B.dylib 0x96d0e0fa semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x96d3bc85 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x96d6aaa8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x916c4d48 -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x9167d9bd -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x9167d8a0 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0129507f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01293e60 -[XTThread run:] + 400
8 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
9 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
10 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
11 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 8:
0 libSystem.B.dylib 0x96d0e0fa semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x96d3bc85 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x96d6aaa8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x916c4d48 -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x9167d9bd -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x9167d8a0 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0129507f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01293e60 -[XTThread run:] + 400
8 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
9 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
10 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
11 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 9:
0 libSystem.B.dylib 0x96d0e09a mach_msg_trap + 10
1 libSystem.B.dylib 0x96d0e807 mach_msg + 68
2 com.apple.CoreFoundation 0x98d1b37f __CFRunLoopRun + 2079
3 com.apple.CoreFoundation 0x98d1a464 CFRunLoopRunSpecific + 452
4 com.apple.CoreFoundation 0x98d1a291 CFRunLoopRunInMode + 97
5 com.apple.Foundation 0x916c2640 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 279
6 com.apple.proxtcore 0x012962f5 -[XTRunLoopThread run:] + 453
7 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
8 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
9 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
10 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 10:
0 libSystem.B.dylib 0x96d0e0fa semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x96d3bc85 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x96d6aaa8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x916c4d48 -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x9167d9bd -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x9167d8a0 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0129507f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01293e60 -[XTThread run:] + 400
8 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
9 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
10 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
11 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 11:
0 libSystem.B.dylib 0x96d0e0fa semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x96d3bc85 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x96d6aaa8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x916c4d48 -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x9167d9bd -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x9167d8a0 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0129507f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01293e60 -[XTThread run:] + 400
8 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
9 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
10 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
11 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 12:
0 libSystem.B.dylib 0x96d0e0fa semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x96d3bc85 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x96d6aaa8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x916c4d48 -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x9167d9bd -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x9167d8a0 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0129507f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01293e60 -[XTThread run:] + 400
8 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
9 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
10 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
11 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 13:
0 libSystem.B.dylib 0x96d0e0fa semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x96d3bc85 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x96d6aaa8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x916c4d48 -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x9167d9bd -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x9167d8a0 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0129507f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01293e60 -[XTThread run:] + 400
8 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
9 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
10 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
11 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 14:
0 libSystem.B.dylib 0x96d0e0fa semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x96d3bc85 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x96d6aaa8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x916c4d48 -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x9167d9bd -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x9167d8a0 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0129507f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01293e60 -[XTThread run:] + 400
8 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
9 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
10 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
11 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 15:
0 libSystem.B.dylib 0x96d0e0fa semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x96d3bc85 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x96d6aaa8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x916c4d48 -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x9167d9bd -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x9167d8a0 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0129507f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01293e60 -[XTThread run:] + 400
8 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
9 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
10 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
11 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 16:
0 libSystem.B.dylib 0x96d0e0fa semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x96d3bc85 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x96d6aaa8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x916c4d48 -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x9167d9bd -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x9167d8a0 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0129507f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01293e60 -[XTThread run:] + 400
8 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
9 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
10 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
11 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 17:
0 libSystem.B.dylib 0x96d0e0fa semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x96d3bc85 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x96d6aaa8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x916c4d48 -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x9167d9bd -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x9167d8a0 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0129507f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01293e60 -[XTThread run:] + 400
8 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
9 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
10 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
11 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 18:
0 libSystem.B.dylib 0x96d0e0fa semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x96d3bc85 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x96d6aaa8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x916c4d48 -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x9167d9bd -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x9167d8a0 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0129507f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01293e60 -[XTThread run:] + 400
8 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
9 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
10 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
11 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 19:
0 libSystem.B.dylib 0x96d0e0fa semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x96d3bc85 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x96d6aaa8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x916c4d48 -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x9167d9bd -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x9167d8a0 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0129507f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01293e60 -[XTThread run:] + 400
8 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
9 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
10 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
11 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 20:
0 libSystem.B.dylib 0x96d0e0fa semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x96d3bc85 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x96d6aaa8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x916c4d48 -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x9167d9bd -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x9167d8a0 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0129507f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01293e60 -[XTThread run:] + 400
8 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
9 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
10 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
11 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 21:
0 libSystem.B.dylib 0x96d0e0fa semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x96d3bc85 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x96d6aaa8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x916c4d48 -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x9167d9bd -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x9167d8a0 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0129507f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01293e60 -[XTThread run:] + 400
8 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
9 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
10 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
11 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 22:
0 libSystem.B.dylib 0x96d0e0fa semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x96d3bc85 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x96d6aaa8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x916c4d48 -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x9167d9bd -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x9167d8a0 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0129507f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01293e60 -[XTThread run:] + 400
8 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
9 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
10 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
11 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 23:
0 libSystem.B.dylib 0x96d0e0fa semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x96d3bc85 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x96d6aaa8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x916c4d48 -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x9167d9bd -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x9167d8a0 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0129507f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01293e60 -[XTThread run:] + 400
8 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
9 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
10 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
11 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 24:
0 libSystem.B.dylib 0x96d0e0fa semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x96d3bc85 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x96d6aaa8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x916c4d48 -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x9167d9bd -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x9167d8a0 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0129507f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01293e60 -[XTThread run:] + 400
8 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
9 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
10 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
11 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 25:
0 libSystem.B.dylib 0x96d0e09a mach_msg_trap + 10
1 libSystem.B.dylib 0x96d0e807 mach_msg + 68
2 com.apple.iLifeSQLAccess 0x0137ba81 -[RALatchTrigger wait] + 81
3 com.apple.iLifeSQLAccess 0x0137b976 -[RAOperationQueueImpl _workThread] + 358
4 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
5 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
6 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
7 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 26:
0 libSystem.B.dylib 0x96d0e09a mach_msg_trap + 10
1 libSystem.B.dylib 0x96d0e807 mach_msg + 68
2 com.apple.iLifeSQLAccess 0x0137ba81 -[RALatchTrigger wait] + 81
3 com.apple.iLifeSQLAccess 0x0137b976 -[RAOperationQueueImpl _workThread] + 358
4 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
5 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
6 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
7 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 27:
0 libSystem.B.dylib 0x96d0e09a mach_msg_trap + 10
1 libSystem.B.dylib 0x96d0e807 mach_msg + 68
2 com.apple.iLifeSQLAccess 0x0137ba81 -[RALatchTrigger wait] + 81
3 com.apple.iLifeSQLAccess 0x0137b976 -[RAOperationQueueImpl _workThread] + 358
4 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
5 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
6 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
7 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 28:
0 libSystem.B.dylib 0x96d0e09a mach_msg_trap + 10
1 libSystem.B.dylib 0x96d0e807 mach_msg + 68
2 com.apple.iLifeSQLAccess 0x0137ba81 -[RALatchTrigger wait] + 81
3 com.apple.iLifeSQLAccess 0x0137b976 -[RAOperationQueueImpl _workThread] + 358
4 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
5 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
6 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
7 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 29:
0 libSystem.B.dylib 0x96d0e09a mach_msg_trap + 10
1 libSystem.B.dylib 0x96d0e807 mach_msg + 68
2 com.apple.iLifeSQLAccess 0x0137ba81 -[RALatchTrigger wait] + 81
3 com.apple.iLifeSQLAccess 0x0137b976 -[RAOperationQueueImpl _workThread] + 358
4 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
5 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
6 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
7 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 30:
0 libSystem.B.dylib 0x96d0e09a mach_msg_trap + 10
1 libSystem.B.dylib 0x96d0e807 mach_msg + 68
2 com.apple.iLifeSQLAccess 0x0137ba81 -[RALatchTrigger wait] + 81
3 com.apple.iLifeSQLAccess 0x0137b976 -[RAOperationQueueImpl _workThread] + 358
4 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
5 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
6 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
7 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 31:
0 libSystem.B.dylib 0x96d0e0fa semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x96d3bc85 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x96d6aaa8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x916c4d48 -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x9167d9bd -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x9167d8a0 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0129507f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01293e60 -[XTThread run:] + 400
8 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
9 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
10 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
11 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 32:
0 libSystem.B.dylib 0x96d0e0fa semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x96d3bc85 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x96d6aaa8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x916c4d48 -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x9167d9bd -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x9167d8a0 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0129507f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01293e60 -[XTThread run:] + 400
8 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
9 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
10 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
11 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 33:
0 libSystem.B.dylib 0x96d0e0fa semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x96d3bc85 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x96d6aaa8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x916c4d48 -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x9167d9bd -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x9167d8a0 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0129507f -[XTMsgQueue waitForMessage] + 47
7 com.apple.proxtcore 0x01293e60 -[XTThread run:] + 400
8 com.apple.Foundation 0x91688ad0 -[NSThread main] + 45
9 com.apple.Foundation 0x91688a80 __NSThread__main__ + 1499
10 libSystem.B.dylib 0x96d3b7fd _pthread_start + 345
11 libSystem.B.dylib 0x96d3b682 thread_start + 34
Thread 34 Crashed:
0 ??? 0x194e4f0a 0 + 424562442
1 GLEngine 0x167c6f03 gleSetVertexSubmitFunc + 179
2 GLEngine 0x167e875d glVertex2f_Exec + 78
3 com.apple.QuartzCore 0x950c4e4b fe_gl_texture_load + 4819
4 com.apple.QuartzCore 0x9505ffc8 fe_context_texture_load + 201
5 com.apple.QuartzCore 0x9505fe76 image_buffer_texture_ref + 209
6 com.apple.QuartzCore 0x9505e13e texture_retain + 413
7 com.apple.QuartzCore 0x9505dd7c fe_texture_new + 573
8 com.apple.QuartzCore 0x9505ca08 fe_tree_create_texture + 1256
9 com.apple.QuartzCore 0x950da5e4 fe_tree_render_unary + 1701
10 com.apple.QuartzCore 0x9505a71e fe_tree_render_ + 706
11 com.apple.QuartzCore 0x9505b90b fe_tree_render_ + 5295
12 com.apple.QuartzCore 0x9505e4a8 fe_tree_render_texture + 60
13 com.apple.QuartzCore 0x9505e2d0 texture_retain + 815
14 com.apple.QuartzCore 0x9505dd7c fe_texture_new + 573
15 com.apple.QuartzCore 0x9505ca08 fe_tree_create_texture + 1256
16 com.apple.QuartzCore 0x9505c08b fe_tree_render_apply + 909
17 com.apple.QuartzCore 0x9505abbb fe_tree_render_ + 1887
18 com.apple.QuartzCore 0x9505e4a8 fe_tree_render_texture + 60
19 com.apple.QuartzCore 0x9505e2d0 texture_retain + 815
20 com.apple.QuartzCore 0x9505dd7c fe_texture_new + 573
21 com.apple.QuartzCore 0x9505ca08 fe_tree_create_texture + 1256
22 com.apple.QuartzCore 0x9505c08b fe_tree_render_apply + 909
23 com.apple.QuartzCore 0x9505abbb fe_tree_render_ + 1887
24 com.apple.QuartzCore 0x9505e4a8 fe_tree_render_texture + 60
25 com.apple.QuartzCore 0x9505e2d0 texture_retain + 815
26 com.apple.QuartzCore 0x9505dd7c fe_texture_new + 573
27 com.apple.QuartzCore 0x9505ca08 fe_tree_create_texture + 1256
28 com.apple.QuartzCore 0x950da5e4 fe_tree_render_unary + 1701
29 com.apple.QuartzCore 0x9505a71e fe_tree_render_ + 706
30 com.apple.QuartzCore 0x9505bbea fe_tree_render_ + 6030
31 com.apple.QuartzCore 0x9505bc42 fe_tree_render_ + 6118
32 com.apple.QuartzCore 0x9505e4a8 fe_tree_render_texture + 60
33 com.apple.QuartzCore 0x9505e2d0 texture_retain + 815
34 com.apple.QuartzCore 0x9505dd7c fe_texture_new + 573
35 com.apple.QuartzCore 0x9505ca08 fe_tree_create_texture + 1256
36 com.apple.QuartzCore 0x9505c08b fe_tree_render_apply + 909
37 com.apple.QuartzCore 0x9505abbb fe_tree_render_ + 1887
38 com.apple.QuartzCore 0x9505e4a8 fe_tree_render_texture + 60
39 com.apple.QuartzCore 0x9505e2d0 texture_retain + 815
40 com.apple.QuartzCore 0x9505dd7c fe_texture_new + 573
41 com.apple.QuartzCore 0x9505ca08 fe_tree_create_texture + 1256
42 com.apple.QuartzCore 0x9505c08b fe_tree_render_apply + 909
43 com.apple.QuartzCore 0x9505abbb fe_tree_render_ + 1887
44 com.apple.QuartzCore 0x9505e4a8 fe_tree_render_texture + 60
45 com.apple.QuartzCore 0x9505e2d0 texture_retain + 815
46 com.apple.QuartzCore 0x9505dd7c fe_texture_new + 573
47 com.apple.QuartzCore 0x9505ca08 fe_tree_create_texture + 1256
48 com.apple.QuartzCore 0x9505c08b fe_tree_render_apply + 909
49 com.apple.QuartzCore 0x9505abbb fe_tree_render_ + 1887
50 com.apple.QuartzCore 0x9505e4a8 fe_tree_render_texture + 60
51 com.apple.QuartzCore 0x9505e2d0 texture_retain + 815
52 com.apple.QuartzCore 0x9505dd7c fe_texture_new + 573
53 com.apple.QuartzCore 0x9505ca08 fe_tree_create_texture + 1256
54 com.apple.QuartzCore 0x9505c08b fe_tree_render_apply + 909
55 com.apple.QuartzCore 0x9505abbb fe_tree_render_ + 1887
56 com.apple.QuartzCore 0x9505e4a8 fe_tree_render_texture + 60
57 com.apple.QuartzCore 0x9505e2d0 texture_retain + 815
58 com.apple.QuartzCore 0x9505dd7c fe_texture_new + 573
59 com.apple.QuartzCore 0x9505ca08 fe_tree_create_texture + 1256
60 com.apple.QuartzCore 0x950da5e4 fe_tree_render_unary + 1701
61 com.apple.QuartzCore 0x9505a71e fe_tree_render_ + 706
62 com.apple.QuartzCore 0x9505bc42 fe_tree_render_ + 6118
63 com.apple.QuartzCore 0x9505bbea fe_tree_render_ + 6030
64 com.apple.QuartzCore 0x9505e4a8 fe_tree_render_texture + 60
65 com.apple.QuartzCore 0x9505e2d0 texture_retain + 815
66 com.apple.QuartzCore 0x9505dd7c fe_texture_new + 573
67 com.apple.QuartzCore 0x9505ca08 fe_tree_create_texture + 1256
68 com.apple.QuartzCore 0x9505c08b fe_tree_render_apply + 909
69 com.apple.QuartzCore 0x9505abbb fe_tree_render_ + 1887
70 com.apple.QuartzCore 0x9505e4a8 fe_tree_render_texture + 60
71 com.apple.QuartzCore 0x9505e2d0 texture_retain + 815
72 com.apple.QuartzCore 0x9505dd7c fe_texture_new + 573
73 com.apple.QuartzCore 0x9505ca08 fe_tree_create_texture + 1256
74 com.apple.QuartzCore 0x9505c08b fe_tree_render_apply + 909
75 com.apple.QuartzCore 0x9505abbb fe_tree_render_ + 1887
76 com.apple.QuartzCore 0x9505e4a8 fe_tree_render_texture + 60
77 com.apple.QuartzCore 0x9505e2d0 texture_retain + 815
78 com.apple.QuartzCore 0x9505dd7c fe_texture_new + 573
79 com.apple.QuartzCore 0x9505ca08 fe_tree_create_texture + 1256
80 com.apple.QuartzCore 0x9505c08b fe_tree_render_apply + 909
81 com.apple.QuartzCore 0x9505abbb fe_tree_render_ + 1887
82 com.apple.QuartzCore 0x9505e4a8 fe_tree_render_texture + 60
83 com.apple.QuartzCore 0x9505e2d0 texture_retain + 815
84 com.apple.QuartzCore 0x9505dd7c fe_texture_new + 573
85 com.apple.QuartzCore 0x9505ca08 fe_tree_create_texture + 1256
86 com.apple.QuartzCore 0x9505c08b fe_tree_render_apply + 909
87 com.apple.QuartzCore 0x9505abbb fe_tree_render_ + 1887
88 com.apple.QuartzCore 0x9505e4a8 fe_tree_render_texture + 60
89 com.apple.QuartzCore 0x9505e2d0 texture_retain + 815
90 com.apple.QuartzCore 0x9505dd7c fe_texture_new + 573
91 com.apple.QuartzCore 0x9505ca08 fe_tree_create_texture + 1256
92 com.apple.QuartzCore 0x9505c08b fe_tree_render_apply + 909
93 com.apple.QuartzCore 0x9505abbb fe_tree_render_ + 1887
94 com.apple.QuartzCore 0x9505e4a8 fe_tree_render_texture + 60
95 com.apple.QuartzCore 0x9505e2d0 texture_retain + 815
96 com.apple.QuartzCore 0x9505dd7c fe_texture_new + 573
97 com.apple.QuartzCore 0x9505ca08 fe_tree_create_texture + 1256
98 com.apple.QuartzCore 0x9505c08b fe_tree_render_apply + 909
99 com.apple.QuartzCore 0x9505abbb fe_tree_render_ + 1887
100 com.apple.QuartzCore 0x9505e4a8 fe_tree_render_texture + 60
101 com.apple.QuartzCore 0x9505e2d0 texture_retain + 815
102 com.apple.QuartzCore 0x9505dd7c fe_texture_new + 573
103 com.apple.QuartzCore 0x9505ca08 fe_tree_create_texture + 1256
104 com.apple.QuartzCore 0x9505c08b fe_tree_render_apply + 909
105 com.apple.QuartzCore 0x9505abbb fe_tree_render_ + 1887
106 com.apple.QuartzCore 0x9505e4a8 fe_tree_render_texture + 60
107 com.apple.QuartzCore 0x9505e2d0 texture_retain + 815
108 com.apple.QuartzCore 0x9505dd7c fe_texture_new + 573
109 com.apple.QuartzCore 0x9505ca08 fe_tree_create_texture + 1256
110 com.apple.QuartzCore 0x9505c08b fe_tree_render_apply + 909
111 com.apple.QuartzCore 0x9505abbb fe_tree_render_ + 1887
112 com.apple.QuartzCore 0x9505e4a8 fe_tree_render_texture + 60
113 com.apple.QuartzCore 0x9505e2d0 texture_retain + 815
114 com.apple.QuartzCore 0x9505dd7c fe_texture_new + 573
115 com.apple.QuartzCore 0x9505ca08 fe_tree_create_texture + 1256
116 com.apple.QuartzCore 0x9505c08b fe_tree_render_apply + 909
117 com.apple.QuartzCore -
How to copy preferences (keywords, layout ecc.) of Aperture?
Hello!
I'm using Aperture in my PowerMac and now also with the MacBook Pro. Is it possibile copy all the program preferences from one location to the other? Preferences like keywords, export pre-set, toolbar setup ecc.? I know that it is possible export, for example, the keywords but after I need to import in the new location... I preefer a system to take all the setups in one time and copy it.
Thank you!
maxOr more in general, how to sync the libraies and vaults without one designated master? I have the same setup as you, Desktop (iMac G5), Laptop (MBpro) and a firewire backup device connected to the G5.
How should one go about to keep all the libraries synchronized? If I change something on the MBpro or on the G5 I want to copy the changes to the other computer as well. If I delete stuff on one machine it should go from the other as well. Under Unix one could use tools like CVS to do this, but it would cost quite a bit of disk space, since that software doesn't know about binary files.
iMac G5 21" Mac OS X (10.4.6) -
Cannot open apps iPhoto and Aperture after updates
Cannot open apps iPhoto and Aperture after updates. I'm operating ML on mbpro. Now apps will not open. Simply that.
Not simple, if as ML implies you are running Mountain Lion! If you only mean Lion, then it would be useful for you to open another User Account, and as that User test to see if either app will launch?
Ernie -
Using Aperture long trip with MB Air
I am a photographer and recently bought a refurb MB Air 11" from Apple. It is 1.4Ghz Core 2 Duo with 2 GB of DDR3 and 3MB of cache. It uses Nvidia Gforce 320M video with 256mb. I am going on a very long trip overseas and bought this to take instead of my MBPro 17" main computer to save space and weight and also for the non volatile memory for downloaded key shots. My main processing tool is Aperture. Since the Air only has 128GB of main ram, I'll be bringing a 500GB Lacie Rugged remote USB drive as the main download tool to connect to the Air. I shoot Nikon and Lumix. Any hints or problems I should look out for? Any thoughts about migration to Lion and potential cloud back up? Thanks.
I am a photographer and recently bought a refurb MB Air 11" from Apple. It is 1.4Ghz Core 2 Duo with 2 GB of DDR3 and 3MB of cache. It uses Nvidia Gforce 320M video with 256mb. I am going on a very long trip overseas and bought this to take instead of my MBPro 17" main computer to save space and weight and also for the non volatile memory for downloaded key shots. My main processing tool is Aperture. Since the Air only has 128GB of main ram, I'll be bringing a 500GB Lacie Rugged remote USB drive as the main download tool to connect to the Air. I shoot Nikon and Lumix. Any hints or problems I should look out for? Any thoughts about migration to Lion and potential cloud back up? Thanks.
-
Aperture 3 Help says it needs Javascript
I've just downloaded the A3 trial onto my MBPro with Leopard 10.5.8. I pulled down the help menu and it says the Help needs to have Javascript enabled.
Where do I enable it? It is enabled in Safari.I know someone already mentioned the online version, but it would be helpful to know if the people having this problem are able to use the one online. I'm not having any problems with Help so I can't test it.
http://documentation.apple.com/en/aperture/usermanual/
Also, are you using Safari 3 or 4?
http://www.apple.com/safari/download/
DLS
Message was edited by: MacDLS
Maybe you are looking for
-
How can I find old recipes from eprint Entree?
I rwecll getting a recipe from eprints sometime in July of this year. I cannot find the recipe but wondered is there an archive section for eprint's Entree app?
-
I am new to JSF...i want to popup a small window in jsf... is there any tag to popup a window in jsf...something similar to woodstock bubble component?
-
How can I uninstall a long-ago expired Adobe XI (11.0.06) trial? During the trial, Ver XI installed itself as my "default", which is still making it difficult for me to access the Adobe X (10.1.10) that I previously purchased.
-
One Master Template for Mulitple InDesign Documents?
For example, say I have a change to a character style, or a page template. I want this change to be reflected in multiple documents that all have the same look. Right now I'm working on a template for a client that has 8 datasheets. Each time they
-
Miix 3 1030 - The battery discharges slowly when adapter is connected
Just as the subject says, the battery level slowly discharges over time even when the adapter is connected while the tablet is running. But when I turn the tablet off, the battery appears to be charging fine. This happens all the time, and it doesn't