HD Load_Cycle_Count, something to worry about?
I installed a brand new 500 GB 7200 rpm Seagate Momentus 7200.4 ST9500420AS hard drive in my Early 2009 Intel Mac mini to replace the failed 1.5 year old 500 GB 5400 rpm Hitachi HTS545050B9SA02 recently. The new Seagate drive works OK.
Then I happened to see some web pages indicating that some HDs might be "pre-programmed" to fail in about 5 years because they too eagerly park their heads every 20 seconds when idling. My brand-new drive had parked its heads about 30.000 times during its first month of moderate use according to smartctl unix tool or Volitans Software's SMART Utility:
http://mymacfixes.blogspot.com/2009/06/how-do-i-stop-clicking-noise-from-hard.ht ml
http://mac.softpedia.com/get/System-Utilities/smartctl.shtml
http://sourceforge.net/apps/trac/smartmontools/wiki
http://www.volitans-software.com/smart_utility.php
The drive spec's seem to indicate that it should take at least 600.000 such Load/Unload Cycles. But at this pace, the drive will meet that figure in two years.
This web page has a cure for that:
http://mymacfixes.blogspot.com/2009/06/how-do-i-stop-clicking-noise-from-hard.ht ml
Now, I'm not sure if this is something an end user should be worried about. Just parking the head without spinning down and up the disk seems inncocent and might be good for laptops that get tossed around. Hitachi has a page describing the technology:
http://www.hitachigst.com/tech/techlib.nsf/techdocs/9076679E3EE4003E86256FAB0058 25FB/$file/LoadUnload_white_paper_FINAL.pdf
Anyway, yesterday I installed hdapm and now the Load_Cycle_Count doesn't grow so fast anymore and the Mac mini works as usual.
http://mckinlay.net.nz/hdapm/
Hi, jmsy. Paying attention to your hard drive's load cycle count is something you absolutely, positively don't need to do. It's like counting the number of times the wheels on your car turn. Sure, there's a relationship there between usage and lifespan. But you're going to use the car as much as you have to, and replace its tires and the car itself when necessary, and you'll know when those things are necessary without counting tire revolutions all along the way.
Back up your hard drive, keep the backup(s) up to date, and replace the drive when it fails (or, perhaps more likely, when your storage needs outgrow it). Forget about load cycles.
Similar Messages
-
Something to worry about or is it just router 'white noise'?
I don't think this is Arch specific, but felt the Newbie Corner would be an appropriate place to make this thread. I apologize in advance if this is a stupid question, but I seem to get a lot of blocked UDP packets from various IP's directed at port 55881 in particular. Occasionally, I'll also get attempted TCP connection requests to port 23, 445, and some ports in the 8000's. If this is something to worry about, what can I do to configure my system so that I can be at ease (or close enough)?
illusory wrote:My logs on my system check out well. The connection attempts I mentioned are all from my router's log. How can I check to make sure there isn't anything running listening in on those ports? What can I do to disable these services if necessary?
As a device, which faces internet, I guess it's normal for the router to detect some connection attempts either by mistake, or from port scanners, kids, etc...
The services run on your machines, not on the router. The only one on the router should be either telnet or httpd for configuration. In order to protect your internal network, you only need to disable remote adminitstration on the router (or whatever it is called in your case, that is the router should be accessible for administration only from the LAN) and port forwarding (also on the router, so that requests are not forwarded to the LAN). Enjoy -
I rec'd an alert that my "Apple ID and phone no. are now being used for iCloud on a new iPhone." I am not using iCloud and I don't have a new iPhone. Is this something to worry about?
Howdy Libbidydooda,
There are a couple of possibilities that may apply to the email you have received regarding your Apple ID. The first is that the email may be a legitimate warning that your Apple ID has been compromised. For this reason I would suggest that you change the password to your Apple ID as soon as possible. Use the instructions on this page -
Apple ID: Changing your password - Apple Support
In order to increase security for your Apple ID you may want to set up and use two-step verification. See this article for information about it -
Frequently asked questions about two-step verification for Apple ID - Apple Support
The second possibilty is that the email is an attempt at "phishing" in order to get you to reveal personal information. Typically this is done with an email that looks like it comes from an official source but has links to web pages that, while they may look like they are real, may actually be gathering your information for use by others. This article has more information about phishing -
Identifying fraudulent "phishing" email - Apple Support
For this reason it is important that you do not follow any links in the email, as they may compromise your security.
Thanks for using Apple Support Communities.
Best,
Brett L -
Does anyone have the problem of their phone always hot?! Sometimes I even get the sign that says my iPhone is too hot. Is this something to worry about?! I was never like this until the recent ios7 upgrades.
It could also be that your battery has gone bad. If your phone is still under warranty, make an appointment at an Apple store. It will take a tech a few minutes to test the battery, and they will replace if for you if it is bad. If not under warranty, search for a repair person in your area.
-
Something to worry about? - Security issue?
iMac
OSX 10.10.1
Transfer of files from a USB Flash Drive
1) - Transferred file from one USB FlashDrive to another USB FlashDrive.
2) - Attempted to eject USB devices - Window appeared stating Finder is using device (it wasn't!) - eventually they were ejected.
3) - Spotlight Search identified a number of MAIL & MESSAGE items (recent emails with subject details)
4) - Could not open these - when I attempted to I got this on the right side of the search window :-
5) - a four digit .emix file (which could not be opened) and below this in grey were the initials sw vers -
underneath this was the message Created Application <DNL>
6) - Attempting to open the .emix file produced a window with the message :-
You do not have permission to open the document " .emix".
Contact your computer or network administrator for assistance..
Has a DNL application been created?
What does this mean if it has?
And ... Is it something for me to worry about?illusory wrote:My logs on my system check out well. The connection attempts I mentioned are all from my router's log. How can I check to make sure there isn't anything running listening in on those ports? What can I do to disable these services if necessary?
As a device, which faces internet, I guess it's normal for the router to detect some connection attempts either by mistake, or from port scanners, kids, etc...
The services run on your machines, not on the router. The only one on the router should be either telnet or httpd for configuration. In order to protect your internal network, you only need to disable remote adminitstration on the router (or whatever it is called in your case, that is the router should be accessible for administration only from the LAN) and port forwarding (also on the router, so that requests are not forwarded to the LAN). Enjoy -
I found this on diagnostics, I assume its just a small crash, as crashes a happen all the time, it's on an iPad mini. I worry a lot about stuff like this, so dont worry me unnecessarily please! :) it is not jail broken.
It's nothing to worry about. It is a crash report. I have them as well. There is no need to concern yourself with those reports unless your iPad is constantly crashing. If it is, you need to do something to try to stop the crashes, and if you can't, then you would need to Contact an Apple Store for help.
Stay away from those diagnostics data reports, use your iPad and enjoy it. -
Something to worry about ? IBM recruiting for Hyperion consultants
Just seem IBM posting about Hyperion. They have Cognos and Hyperion is their rival product.
Does this seem strange ?Was it for IBM Global Services by any chance? They have a Hyperion practice, or least they did a year or so ago.
A quick Google search shows a bunch of hits in India. Perhaps they are starting up an offshore EPM staffing business? Good luck on that...
Regards,
Cameron Lackpour -
Is this kernel msg something to worry about?
I saw this tonight:
7/15/09 8:46:36 PM SystemUIServer[105] Error: Apple80211Scan() error 16
7/15/09 8:46:36 PM SystemUIServer[105] Error: __performScan() EBUSY, try again in a sec
7/15/09 8:46:37 PM SystemUIServer[105] Error: Apple80211Scan() error 16
7/15/09 8:46:37 PM SystemUIServer[105] Error: __performScan() EBUSY, try again in a sec
I know it is tied to the wireless, does that mean there is a problem with my network card?
I have a macbook pro 17" (June 09 model)
Thanks all for any help!Jerome
Here is the direct download for the program.
http://homepage.mac.com/vinyllife/.cv/vinyllife/Sites/.Public/NoHDClickObjC.app- zip.zip
My harddrive is listed as FUJITSU MHW2120BH in the system info.
Mac OS X (10.3.8) -
Dump Analysis: High ITAB-name-numbers - s.th. to worry about?
Hi Folks,
I'm currently involved with a project implementing SAP CRM-Service and while analysing some dumps for error TSV_TNEW_OCCURS_NO_ROLL_MEMORY I noticed that the number of lines in the internal tables wasn't all that high but that the internally assigned numbers for the itab-names where a lot higher than anything I have seen so far. I'm therefore now wondering if this is something to worry about or if this "normal" for a CRM-Service system.
SAP kernel....... 700 /
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
Memory consumption
Roll.... 6236416
EM...... 2002809728
Heap.... 1362478816
Page.... 32768
MM Used. 3332838064
MM Free. 35308232
Program............. "SAPLIBINF"
Screen.............. "SAPMSSY0 1000"
Termination occurred in the ABAP program "SAPLIBINF" - in
"INST_INSERT_IN_BUFFER".
37 * update the secondary indices
INSERT i_ibinwa_rec INTO TABLE l_ibinwa_tab.
I_IBINWA_TAB
Table IT_199444325(2x536)
C_IBINWA_TAB
Table IT_199443596(4x536)
L_IBINWA_TAB
Table IT_199444327(0x536)
C_IBINWA_SEC_IBASE_STAB
Table IT_199443697(3x124)
I'm used to seeing eg. IT_123 but not these 9 digits long numbers. As the routine this abended in is called from one of our custom-programs I'm just a bit concerned that some internal tables might not be properly cleared/refreshed/freed after usage.
Thanks for any feedback you have!
Cheers
Baerbel
P.S.: I'm sorry for not participating more in the forums but work just keeps interfering!Hi Samuel,
thanks for your quick reply!
To answer your question, I_IBINWA_REC is just a workarea not an internal table. And all the tables I see in the dump-information don't have many entries, they seem all to be in the 1 or at most 2-digit range. This low number of entries compared to the high number of itab-names is what actually had me worried. Something has to be filling up the available memory and I'd like to pinpoint what it is.
It is possible that the program got squeezed from all sides as it abended during conversion activity with lots of activity in the system.
I am glad to read, though, that these high itab-numbers are seen elsewhere as well!
Cheers
Baerbel -
Can anyone tell me if this is something i should worry about?
I just repaired permissions and it says this about ARD.
Is this something i should worry about?
Repairing permissions for “MacBook Pro”
Reading permissions database.
Reading the permissions database can take several minutes.
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
Group differs on "private/etc/cups", should be 0, group is 26.
Permissions repair complete
Repairing permissions for “MacBook Pro”
Reading permissions database.
Reading the permissions database can take several minutes.
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
Group differs on "private/etc/cups", should be 0, group is 26.
Permissions repair completethese messages are harmless and should be ignored. the ARD message one indicates that you might not be running the latest version of leopard. is that right? your profile does indicate 10.5.5 which is the latest.
http://support.apple.com/kb/TS1448?viewlocale=en_US -
Do I need to worry about this?
It has been an interesting few months with my one year old 13" MBP. Lots of spinning beach balls followed by a hard drive crash. Apple was quick to replace the hard drive. And as I had everything backed up on Time Machine I was able to quickly restore everything.
All was good for a few months until the beachballs, freezes, and finder crahes began again. Made another trip to the Genius bar where they thought I might have re-downloaded a corrupt file from Time Machine. They cleaned my temp files and caches and things seemed to work well in the store.
When I returned home I had the same issues. They had prepared me for this. So a system restore, a re mount and re start of time capsule and everything seems to be working well. Speedy, no crashes, no freezes.
The issue is that I wanted to double check so I ran disk verify and permission verify on the disk utility. To my surprise it came back with a LONG error log as below. So long, I could not get it all into this post. But it seems like a recurrent message. Do I need to worry about any of this? What should I do next, if anything? Thanks in advance for your response.
Verifying volume “Macintosh HD”
Performing live verification.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking volume bitmap.
Checking volume information.
Invalid volume file count
(It should be 624512 instead of 624514)
Invalid volume directory count
(It should be 172781 instead of 172779)
The volume Macintosh HD was found corrupt and needs to be repaired.
Error: This disk needs to be repaired. Start up your computer with another disk (such as your Mac OS X installation disc), and then use Disk Utility to repair this disk.
Verify permissions for “Macintosh HD”
Group differs on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AAUAdvanced.nib/keyedobjects.nib", should be 0, group is 80.
Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AAUAdvanced.nib/keyedobjects.nib", should be -rw-r--r-- , they are -rw-rw-r-- .
Group differs on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AAUAssistant.nib/keyedobjects.nib", should be 0, group is 80.
Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AAUAssistant.nib/keyedobjects.nib", should be -rw-r--r-- , they are -rw-rw-r-- .
Group differs on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AAUDocument.nib/keyedobjects.nib", should be 0, group is 80.
Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AAUDocument.nib/keyedobjects.nib", should be -rw-r--r-- , they are -rw-rw-r-- .
Group differs on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AAUDrives.nib/keyedobjects.nib", should be 0, group is 80.
Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AAUDrives.nib/keyedobjects.nib", should be -rw-r--r-- , they are -rw-rw-r-- .
Group differs on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AAUStatisticsPanel.nib/keyedobjects.nib ", should be 0, group is 80.
Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AAUStatisticsPanel.nib/keyedobjects.nib ", should be -rw-r--r-- , they are -rw-rw-r-- .
Group differs on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AAUTaskSheet.nib/keyedobjects.nib", should be 0, group is 80.
Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AAUTaskSheet.nib/keyedobjects.nib", should be -rw-r--r-- , they are -rw-rw-r-- .
Group differs on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AAUTasks.strings", should be 0, group is 80.
Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AAUTasks.strings", should be -rw-r--r-- , they are -rw-rw-r-- .
Group differs on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AAUWirelessPanel.nib/keyedobjects.nib", should be 0, group is 80.
Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AAUWirelessPanel.nib/keyedobjects.nib", should be -rw-r--r-- , they are -rw-rw-r-- .
Group differs on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/APPanels.nib/keyedobjects.nib", should be 0, group is 80.
Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/APPanels.nib/keyedobjects.nib", should be -rw-r--r-- , they are -rw-rw-r-- .
Group differs on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AUFirmwareDownloader.nib/keyedobjects.n ib", should be 0, group is 80.
Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AUFirmwareDownloader.nib/keyedobjects.n ib", should be -rw-r--r-- , they are -rw-rw-r-- .
Group differs on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AirPortAssistant.strings", should be 0, group is 80.
Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AirPortAssistant.strings", should be -rw-r--r-- , they are -rw-rw-r-- .
Group differs on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AirPortErrors.strings", should be 0, group is 80.
Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AirPortErrors.strings", should be -rw-r--r-- , they are -rw-rw-r-- .
Group differs on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AirPortSettings.strings", should be 0, group is 80.
Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AirPortSettings.strings", should be -rw-r--r-- , they are -rw-rw-r-- .
Group differs on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AirPortTimeZones.strings", should be 0, group is 80.
Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AirPortTimeZones.strings", should be -rw-r--r-- , they are -rw-rw-r-- .
Group differs on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AirPortUtilityHelp/AirPortUtilityHelp.h elpindex", should be 0, group is 80.
Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AirPortUtilityHelp/AirPortUtilityHelp.h elpindex", should be -rw-r--r-- , they are -rw-rw-r-- .
Group differs on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AirPortUtilityHelp/AirPortUtilityHelp.h tml", should be 0, group is 80.
Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AirPortUtilityHelp/AirPortUtilityHelp.h tml", should be -rw-r--r-- , they are -rw-rw-r-- .Scott Adelman wrote:
The issue is that I wanted to double check so I ran disk verify and permission verify on the disk utility. To my surprise it came back with a LONG error log as below. So long, I could not get it all into this post. But it seems like a recurrent message. Do I need to worry about any of this? What should I do next, if anything?
Verifying volume “Macintosh HD”
Invalid volume file count
(It should be 624512 instead of 624514)
Invalid volume directory count
(It should be 172781 instead of 172779)
The volume Macintosh HD was found corrupt and needs to be repaired.
Error: This disk needs to be repaired. Start up your computer with another disk (such as your Mac OS X installation disc), and then use Disk Utility to repair this disk.
You definitely need to repair your disk. If you can, boot from something else, such an external disk or the system discs that came with your Mac. You can also cause the disk to be repaired by booting into "Safe Mode": http://support.apple.com/kb/ht1564 . If that process can't repair your disk, you may need one of the more-powerful disk utilities such as Disk Warrior.
Verify permissions for “Macintosh HD”
Group differs on "Applications/Utilities/AirPort Utility.app/Contents/Resources/pl.lproj/AAUAdvanced.nib/keyedobjects.nib", should be 0, group is 80.
You can ignore most permissions repair messages:
http://support.apple.com/kb/TS1448 -
Do I need to worry about these event handlers in a grid from a memory leak perspective?
I'm pretty new to Flex and coudn't figure out how to add event handlers to inline item renderer components from the containing file script so I attached the listnerers simply as part of the components themselves (eg <mx:Checkbox ... chnage="outerDocument.doSomething(event)"../>):
<mx:DataGrid id="targetsGrid" width="100%" height="100%" doubleClickEnabled="true" styleName="itemCell"
headerStyleName="headerRow" dataProvider="{targets}"
rowHeight="19" fontSize="11" paddingBottom="0" paddingTop="1">
<mx:columns>
<mx:DataGridColumn width="78" dataField="@isSelected" headerText="">
<mx:itemRenderer>
<mx:Component>
<mx:HBox width="100%" height="100%" horizontalAlign="center">
<mx:CheckBox id="targetCheckBox" selected="{data.@isSelected == 'true'}"
change="outerDocument.checkChangeHandler(event);"/>
<mx:Image horizontalAlign="center" toolTip="Delete" source="@Embed('/assets/icons/delete.png')" useHandCursor="true" buttonMode="true"
click="outerDocument.deleteHandler(event);"/>
<mx:Image id="editButton" horizontalAlign="center" toolTip="Edit" source="@Embed('/assets/icons/edit-icon.png')" useHandCursor="true" buttonMode="true"
click="outerDocument.editHandler(event);"/>
</mx:HBox>
</mx:Component>
</mx:itemRenderer>
</mx:DataGridColumn>
<mx:DataGridColumn id="Name" dataField="@collectionDesc" headerText="Name" itemRenderer="com.foobar.integrated.media.ui.component.CellStyleForTargetName"/>
<mx:DataGridColumn id="Created" width="140" dataField="@createDateTime" headerText="Created" labelFunction="UiHelper.gridDateFormat" />
</mx:columns>
</mx:DataGrid>
This grid is part of a view that will get destroyed and recreated potentially many times during a user's session within the application (there's a large dynamic nature to the app and views are created at run-time.) By destroyed I mean that the view that holds the above datagrid will no longer be referenced under certain circumstances and an entire new view object is created (meaning the old datagrid is no longer refernced and a new one is created.)
I heard you should clean up event handlers when they are no longer used, and I know at what point the view is destroyed, but I don't know how to clean up the event handlers added to the item renderer components? Is it something that the Flex garbage collector will handle efficiently?
Also, on a somewhat related note, how could I push the item renderer to an external component since in my event handlers for the item renderer buttons I need a reference to the datagrid.selectedIndex which, as an external item renderer I wouldn't have access to this containing grid?No. You don't need explicit cleanup in this case: if your outerDocument is going away, you have nothing to worry about. The event handler leak can happen in sort of the reverse situation: suppose you have a long-lived MyView that contains a custom DataGrid like the one below. Now suppose that MyView frequently destroys and re-creates the grid. And suppose that on its creationComplete event, the grid registers a listener for outerDocument's (MyView's) enterFrame Event. Unless you explicitly remove this listener, MyView will still have a reference to it even after the grid that registered the listener is destroyed (and garbage collected).
This is a pretty contrived example, but it sort of illustrates the potential for leaks: a certain component is elligible for garbage collection, but some longer-lived component holds a reference to it (or part of it, such as a listener function). If the longer-lived component is elligible for GC as well, you don't really need to worry about proper cleanup. That's what you're paying the GC processor cycles for. -
I'm new to the MAC world. I turned my computer on from 'sleep' mode, and a window was up stating that the IOS disk was full; asked me to force quit, then it just froze. It's been 2 hours. Help! I'm worried about losing photos/videos of my children. Im not sure if there's something special I need to do once I turn it back on; in the meantime, its still on... which I'm afraid the picture on the screen will burn into the screen. Does that happen on iMac's? Thx!
Try a hard reset. ( holding Power til it restarts)
Once to your desktop. Click the Apple icon >> About this mac >> More info>> Storage
Once you see what you have the most of. Try to see what you can delete.
Open up any folder>>all files>> or buy an external to store more data.
Once deleting make sure you empty your trash.
If you are new and its a new computer, you might need to bring it to a store for further assistence.
Coast Guard Mechanic w/ an Apple Problem -
Hi. My iPhoto has "quit unexpectedly" and won't reopen (despite many desperate attempts). I am worried about losing my photos as I haven't backed up for a while. Any help would be greatly appreciated.
PROBLEM DETAILS AND SYSTEM CONFIGURATION:
Process: iPhoto [825]
Path: /Applications/iPhoto.app/Contents/MacOS/iPhoto
Identifier: com.apple.iPhoto
Version: 9.2.2 (9.2.2)
Build Info: iPhotoProject-629040000000000~2
App Item ID: 408981381
App External ID: 6836991
Code Type: X86 (Native)
Parent Process: launchd [118]
Date/Time: 2013-11-08 12:31:39.864 +0800
OS Version: Mac OS X 10.7.5 (11G63)
Report Version: 9
Interval Since Last Report: 22527 sec
Crashes Since Last Report: 9
Per-App Interval Since Last Report: 185 sec
Per-App Crashes Since Last Report: 9
Anonymous UUID: 6378AE7B-3F2F-449A-92A6-4A0165586E69
Crashed Thread: 33 Dispatch queue: com.apple.root.default-priority
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: 0x000000000000000a, 0x0000000010e49000
VM Regions Near 0x10e49000:
MALLOC_LARGE 0000000010e01000-0000000010e31000 [ 192K] rw-/rwx SM=PRV
--> mapped file 0000000010e41000-0000000010e52000 [ 68K] r--/rwx SM=COW /Users/USER/Pictures/*/*.jpg
mapped file 0000000010e6d000-000000001101d000 [ 1728K] r--/rwx SM=COW /System/Library/Fonts/LucidaGrande.ttc
Application Specific Information:
objc[825]: garbage collection is OFF
Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x9af9883e __psynch_cvwait + 10
1 libsystem_c.dylib 0x94cace21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x94c5d42c pthread_cond_wait$UNIX2003 + 71
3 com.apple.Foundation 0x9b5e3768 -[__NSOperationInternal waitUntilFinished] + 145
4 com.apple.Foundation 0x9b5e36d0 -[NSOperation waitUntilFinished] + 67
5 com.apple.iPhoto 0x008183ce 0x1000 + 8483790
6 com.apple.iPhoto 0x0006772c 0x1000 + 419628
7 com.apple.iPhoto 0x00065e7e 0x1000 + 413310
8 com.apple.iPhoto 0x0007a54d 0x1000 + 496973
9 com.apple.iPhoto 0x0002794c 0x1000 + 158028
10 com.apple.iPhoto 0x000216af 0x1000 + 132783
11 com.apple.iPhoto 0x00020bb1 0x1000 + 129969
12 com.apple.iPhoto 0x0092a1f4 0x1000 + 9605620
13 com.apple.iPhoto 0x00084617 0x1000 + 538135
14 com.apple.iPhoto 0x0024855c 0x1000 + 2389340
15 com.apple.iPhoto 0x0003416e 0x1000 + 209262
16 com.apple.Foundation 0x9b58ddf1 __-[NSNotificationCenter addObserver:selector:name:object:]_block_invoke_1 + 49
17 com.apple.CoreFoundation 0x90188903 ___CFXNotificationPost_block_invoke_1 + 275
18 com.apple.CoreFoundation 0x90153688 _CFXNotificationPost + 2776
19 com.apple.Foundation 0x9b578fde -[NSNotificationCenter postNotificationName:object:userInfo:] + 92
20 com.apple.AppKit 0x96c71ba9 -[NSApplication _postDidFinishNotification] + 259
21 com.apple.AppKit 0x96c7189f -[NSApplication _sendFinishLaunchingNotification] + 84
22 com.apple.AppKit 0x96c703c0 -[NSApplication(NSAppleEventHandling) _handleAEOpenEvent:] + 277
23 com.apple.AppKit 0x96c700d6 -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 377
24 com.apple.CoreFoundation 0x901a11c8 -[NSObject performSelector:withObject:withObject:] + 72
25 com.apple.Foundation 0x9b5b30c2 __-[NSAppleEventManager setEventHandler:andSelector:forEventClass:andEventID:]_block_invoke_1 + 121
26 com.apple.Foundation 0x9b5b1e75 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 476
27 com.apple.Foundation 0x9b5b1c49 _NSAppleEventManagerGenericHandler + 234
28 com.apple.AE 0x91425045 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned long, unsigned char*) + 202
29 com.apple.AE 0x9140eb67 _ZL25dispatchEventAndSendReplyPK6AEDescPS_ + 43
30 com.apple.AE 0x9140ea54 aeProcessAppleEvent + 253
31 com.apple.HIToolbox 0x916c3a86 AEProcessAppleEvent + 103
32 com.apple.AppKit 0x96c6d157 _DPSNextEvent + 1301
33 com.apple.AppKit 0x96c6c752 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 113
34 com.apple.AppKit 0x96c68ac1 -[NSApplication run] + 911
35 com.apple.AppKit 0x96ef9ac5 NSApplicationMain + 1054
36 com.apple.iPhoto 0x00010dda 0x1000 + 64986
37 com.apple.iPhoto 0x00010269 0x1000 + 62057
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x9af9990a kevent + 10
1 libdispatch.dylib 0x9b938e04 _dispatch_mgr_invoke + 969
2 libdispatch.dylib 0x9b937853 _dispatch_mgr_thread + 53
Thread 2:
0 libsystem_kernel.dylib 0x9af9883e __psynch_cvwait + 10
1 libsystem_c.dylib 0x94cace78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x94cacf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9b6083c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9b5ce7d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9b5ce6a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0176e5e2 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x0176d590 -[XTThread run:] + 416
8 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
9 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
11 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 3:
0 libsystem_kernel.dylib 0x9af96c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9af961f6 mach_msg + 70
2 com.apple.CoreFoundation 0x901359da __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x9013eb04 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x9013e1dc CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x9013e088 CFRunLoopRunInMode + 120
6 com.apple.Foundation 0x9b5824af -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 273
7 com.apple.proxtcore 0x0176f9cd -[XTRunLoopThread run:] + 509
8 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
9 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
11 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 4:
0 libsystem_kernel.dylib 0x9af96c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9af961f6 mach_msg + 70
2 com.apple.CoreFoundation 0x901359da __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x9013eb04 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x9013e1dc CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x9013e088 CFRunLoopRunInMode + 120
6 com.apple.Foundation 0x9b5824af -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 273
7 com.apple.proxtcore 0x0176f9cd -[XTRunLoopThread run:] + 509
8 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
9 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
11 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 5:: Dispatch queue: com.apple.root.default-priority
0 libsystem_kernel.dylib 0x9af98876 __psynch_mutexwait + 10
1 libsystem_c.dylib 0x94ca76af pthread_mutex_lock + 633
2 com.apple.Foundation 0x9b5807f2 -[NSLock lock] + 185
3 com.apple.iPhoto 0x002557bd 0x1000 + 2443197
4 com.apple.CoreFoundation 0x901a0a9d __invoking___ + 29
5 com.apple.CoreFoundation 0x901a09d9 -[NSInvocation invoke] + 137
6 com.apple.Foundation 0x9b6a861a -[NSInvocationOperation main] + 267
7 com.apple.Foundation 0x9b5c31cb -[__NSOperationInternal start] + 797
8 com.apple.Foundation 0x9b5c2ea7 -[NSOperation start] + 67
9 com.apple.Foundation 0x9b5d6ffa ____NSOQSchedule_block_invoke_2 + 135
10 libdispatch.dylib 0x9b936fbd _dispatch_call_block_and_release + 15
11 libdispatch.dylib 0x9b93801c _dispatch_worker_thread2 + 231
12 libsystem_c.dylib 0x94caab24 _pthread_wqthread + 346
13 libsystem_c.dylib 0x94cac6fe start_wqthread + 30
Thread 6:: com.apple.appkit-heartbeat
0 libsystem_kernel.dylib 0x9af98bb2 __semwait_signal + 10
1 libsystem_c.dylib 0x94c5d7b9 nanosleep$UNIX2003 + 187
2 libsystem_c.dylib 0x94c5d558 usleep$UNIX2003 + 60
3 com.apple.AppKit 0x96eb16da -[NSUIHeartBeat _heartBeatThread:] + 2399
4 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
5 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
6 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
7 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 7:
0 libsystem_kernel.dylib 0x9af9883e __psynch_cvwait + 10
1 libsystem_c.dylib 0x94cace78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x94cacf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9b6083c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9b5ce7d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9b5ce6a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0176e5e2 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x0176d590 -[XTThread run:] + 416
8 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
9 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
11 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 8:
0 libsystem_kernel.dylib 0x9af9883e __psynch_cvwait + 10
1 libsystem_c.dylib 0x94cace78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x94cacf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9b6083c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9b5ce7d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9b5ce6a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0176e5e2 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x0176d590 -[XTThread run:] + 416
8 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
9 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
11 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 9:
0 libsystem_kernel.dylib 0x9af9883e __psynch_cvwait + 10
1 libsystem_c.dylib 0x94cace78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x94cacf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9b6083c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9b5ce7d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9b5ce6a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0176e5e2 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x0176d590 -[XTThread run:] + 416
8 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
9 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
11 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 10:
0 libsystem_kernel.dylib 0x9af9883e __psynch_cvwait + 10
1 libsystem_c.dylib 0x94cace78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x94cacf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9b6083c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9b5ce7d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9b5ce6a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0176e5e2 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x0176d590 -[XTThread run:] + 416
8 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
9 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
11 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 11:
0 libsystem_kernel.dylib 0x9af96c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9af961f6 mach_msg + 70
2 com.apple.CoreFoundation 0x901359da __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x9013eb04 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x9013e1dc CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x9013e088 CFRunLoopRunInMode + 120
6 com.apple.Foundation 0x9b5824af -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 273
7 com.apple.proxtcore 0x0176f9cd -[XTRunLoopThread run:] + 509
8 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
9 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
11 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 12:
0 libsystem_kernel.dylib 0x9af9883e __psynch_cvwait + 10
1 libsystem_c.dylib 0x94cace78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x94cacf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9b6083c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9b5ce7d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9b5ce6a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0176e5e2 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x0176d590 -[XTThread run:] + 416
8 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
9 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
11 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 13:
0 libsystem_kernel.dylib 0x9af9883e __psynch_cvwait + 10
1 libsystem_c.dylib 0x94cace78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x94cacf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9b6083c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9b5ce7d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9b5ce6a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0176e5e2 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x0176d590 -[XTThread run:] + 416
8 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
9 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
11 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 14:
0 libsystem_kernel.dylib 0x9af9883e __psynch_cvwait + 10
1 libsystem_c.dylib 0x94cace78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x94cacf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9b6083c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9b5ce7d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9b5ce6a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0176e5e2 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x0176d590 -[XTThread run:] + 416
8 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
9 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
11 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 15:
0 libsystem_kernel.dylib 0x9af9883e __psynch_cvwait + 10
1 libsystem_c.dylib 0x94cace78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x94cacf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9b6083c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9b5ce7d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9b5ce6a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0176e5e2 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x0176d590 -[XTThread run:] + 416
8 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
9 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
11 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 16:
0 libsystem_kernel.dylib 0x9af9883e __psynch_cvwait + 10
1 libsystem_c.dylib 0x94cace78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x94cacf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9b6083c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9b5ce7d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9b5ce6a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0176e5e2 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x0176d590 -[XTThread run:] + 416
8 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
9 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
11 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 17:
0 libsystem_kernel.dylib 0x9af9883e __psynch_cvwait + 10
1 libsystem_c.dylib 0x94cace78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x94cacf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9b6083c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9b5ce7d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9b5ce6a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0176e5e2 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x0176d590 -[XTThread run:] + 416
8 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
9 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
11 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 18:
0 libsystem_kernel.dylib 0x9af9883e __psynch_cvwait + 10
1 libsystem_c.dylib 0x94cace78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x94cacf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9b6083c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9b5ce7d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9b5ce6a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0176e5e2 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x0176d590 -[XTThread run:] + 416
8 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
9 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
11 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 19:
0 libsystem_kernel.dylib 0x9af9883e __psynch_cvwait + 10
1 libsystem_c.dylib 0x94cace78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x94cacf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9b6083c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9b5ce7d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9b5ce6a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0176e5e2 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x0176d590 -[XTThread run:] + 416
8 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
9 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
11 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 20:
0 libsystem_kernel.dylib 0x9af9883e __psynch_cvwait + 10
1 libsystem_c.dylib 0x94cace78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x94cacf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9b6083c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9b5ce7d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9b5ce6a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0176e5e2 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x0176d590 -[XTThread run:] + 416
8 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
9 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
11 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 21:
0 libsystem_kernel.dylib 0x9af9883e __psynch_cvwait + 10
1 libsystem_c.dylib 0x94cace78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x94cacf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9b6083c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9b5ce7d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9b5ce6a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0176e5e2 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x0176d590 -[XTThread run:] + 416
8 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
9 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
11 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 22:
0 libsystem_kernel.dylib 0x9af9883e __psynch_cvwait + 10
1 libsystem_c.dylib 0x94cace78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x94cacf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9b6083c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9b5ce7d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9b5ce6a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0176e5e2 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x0176d590 -[XTThread run:] + 416
8 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
9 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
11 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 23:
0 libsystem_kernel.dylib 0x9af9883e __psynch_cvwait + 10
1 libsystem_c.dylib 0x94cace78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x94cacf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9b6083c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9b5ce7d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9b5ce6a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0176e5e2 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x0176d590 -[XTThread run:] + 416
8 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
9 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
11 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 24:
0 libsystem_kernel.dylib 0x9af9883e __psynch_cvwait + 10
1 libsystem_c.dylib 0x94cace78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x94cacf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9b6083c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9b5ce7d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9b5ce6a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0176e5e2 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x0176d590 -[XTThread run:] + 416
8 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
9 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
11 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 25:
0 libsystem_kernel.dylib 0x9af9883e __psynch_cvwait + 10
1 libsystem_c.dylib 0x94cace78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x94cacf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9b6083c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9b5ce7d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9b5ce6a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x0176e5e2 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x0176d590 -[XTThread run:] + 416
8 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
9 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
11 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 26:: JavaScriptCore::Marking
0 libsystem_kernel.dylib 0x9af9883e __psynch_cvwait + 10
1 libsystem_c.dylib 0x94cace21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x94c5d42c pthread_cond_wait$UNIX2003 + 71
Thread 27:: JavaScriptCore::Marking
0 libsystem_kernel.dylib 0x9af9883e __psynch_cvwait + 10
1 libsystem_c.dylib 0x94cace21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x94c5d42c pthread_cond_wait$UNIX2003 + 71
Thread 28:: JavaScriptCore::Marking
0 libsystem_kernel.dylib 0x9af9883e __psynch_cvwait + 10
1 libsystem_c.dylib 0x94cace21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x94c5d42c pthread_cond_wait$UNIX2003 + 71
Thread 29:: JavaScriptCore::BlockFree
0 libsystem_kernel.dylib 0x9af9883e __psynch_cvwait + 10
1 libsystem_c.dylib 0x94cace21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x94c5d3e0 pthread_cond_timedwait$UNIX2003 + 70
3 com.apple.JavaScriptCore 0x9665361c ***::ThreadCondition::timedWait(***::Mutex&, double) + 156
4 com.apple.JavaScriptCore 0x968a0b93 JSC::Heap::blockFreeingThreadMain() + 323
5 com.apple.JavaScriptCore 0x968a0bcf JSC::Heap::blockFreeingThreadStartFunc(void*) + 15
6 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
7 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 30:
0 libsystem_kernel.dylib 0x9af96c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9af961f6 mach_msg + 70
2 com.apple.iLifeSQLAccess 0x01860f41 -[RALatchTrigger wait] + 81
3 com.apple.iLifeSQLAccess 0x01860dc9 -[RAOperationQueueImpl _workThread] + 217
4 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
5 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
6 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
7 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 31:
0 libsystem_kernel.dylib 0x9af96c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9af961f6 mach_msg + 70
2 com.apple.iLifeSQLAccess 0x01860f41 -[RALatchTrigger wait] + 81
3 com.apple.iLifeSQLAccess 0x01860dc9 -[RAOperationQueueImpl _workThread] + 217
4 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
5 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
6 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
7 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 32:
0 libsystem_kernel.dylib 0x9af9883e __psynch_cvwait + 10
1 libsystem_c.dylib 0x94cace78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x94cacf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9b6083c3 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9b5ce7d2 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9b5ce6a6 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.RedRock 0x01d4f331 -[RKAsyncImageRenderer _backgroundRenderThread:] + 177
7 com.apple.CoreFoundation 0x901a61aa -[NSObject performSelector:] + 58
8 com.apple.proxtcore 0x01778506 -[XTThreadSendOnlyDetached _detachedMessageHandler:] + 166
9 com.apple.CoreFoundation 0x9019dd11 -[NSObject performSelector:withObject:] + 65
10 com.apple.proxtcore 0x0176fb95 -[XTSubscription postMessage:] + 181
11 com.apple.proxtcore 0x0176f2e6 -[XTDistributor distributeMessage:] + 726
12 com.apple.proxtcore 0x0176ee35 -[XTThread handleMessage:] + 1285
13 com.apple.proxtcore 0x0176d5a6 -[XTThread run:] + 438
14 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
15 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
16 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
17 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 33 Crashed:: Dispatch queue: com.apple.root.default-priority
0 libsystem_c.dylib 0x94c80a91 memmove$VARIANT$sse42 + 212
1 com.apple.ImageIO.framework 0x9038512b CGImageReadGetBytesAtOffset + 857
2 com.apple.ImageIO.framework 0x90384dc4 CGImageReadSessionGetBytes + 47
3 com.apple.ImageIO.framework 0x90384c9f fill_input_buffer + 223
4 libJPEG.dylib 0x95d01f1a decode_mcu_optimized + 2748
5 libJPEG.dylib 0x95d012c9 decompress_onepass + 174
6 libJPEG.dylib 0x95d011bc process_data_simple_main + 43
7 libJPEG.dylib 0x95d01186 _cg_jpeg_read_scanlines + 154
8 com.apple.ImageIO.framework 0x90389014 copyImageBlockSetJPEG + 2807
9 com.apple.ImageIO.framework 0x90388456 ImageProviderCopyImageBlockSetCallback + 440
10 com.apple.CoreGraphics 0x9ba8dd98 CGImageProviderCopyImageBlockSetWithOptions + 173
11 com.apple.CoreGraphics 0x9ba8dce5 CGImageProviderCopyImageBlockSet + 69
12 com.apple.CoreGraphics 0x9ba8d848 img_blocks_create + 332
13 com.apple.CoreGraphics 0x9babc3a6 img_blocks_extent + 73
14 com.apple.CoreGraphics 0x9babc351 img_extent + 28
15 com.apple.CoreGraphics 0x9ba045b3 img_data_lock + 7949
16 com.apple.CoreGraphics 0x9ba8cc5c CGSImageDataLock + 165
17 libRIP.A.dylib 0x9035661d ripc_AcquireImage + 1901
18 libRIP.A.dylib 0x90354e6f ripc_DrawImage + 951
19 com.apple.CoreGraphics 0x9ba8c855 CGContextDrawImage + 457
20 com.apple.iPhoto 0x0009e051 0x1000 + 643153
21 com.apple.iPhoto 0x008b033b 0x1000 + 9106235
22 com.apple.iPhoto 0x008afcfe 0x1000 + 9104638
23 com.apple.iPhoto 0x0081fe56 0x1000 + 8515158
24 com.apple.Foundation 0x9b5c31cb -[__NSOperationInternal start] + 797
25 com.apple.Foundation 0x9b5c2ea7 -[NSOperation start] + 67
26 com.apple.Foundation 0x9b5d6ffa ____NSOQSchedule_block_invoke_2 + 135
27 libdispatch.dylib 0x9b936fbd _dispatch_call_block_and_release + 15
28 libdispatch.dylib 0x9b93801c _dispatch_worker_thread2 + 231
29 libsystem_c.dylib 0x94caab24 _pthread_wqthread + 346
30 libsystem_c.dylib 0x94cac6fe start_wqthread + 30
Thread 34:: Dispatch queue: NSPersistentUI I/O
0 libsystem_kernel.dylib 0x9af98f5e __unlink + 10
1 libsystem_kernel.dylib 0x9af97c02 unlink + 18
2 libremovefile.dylib 0x915d8aae __removefile_process_file + 366
3 libremovefile.dylib 0x915d8bb0 __removefile_tree_walker + 176
4 libremovefile.dylib 0x915d79f7 removefile + 140
5 com.apple.Foundation 0x9b5c486c -[NSFilesystemItemRemoveOperation main] + 250
6 com.apple.Foundation 0x9b5c31cb -[__NSOperationInternal start] + 797
7 com.apple.Foundation 0x9b5c2ea7 -[NSOperation start] + 67
8 com.apple.Foundation 0x9b5c2254 -[NSFileManager removeItemAtPath:error:] + 99
9 com.apple.Foundation 0x9b5c21b6 -[NSFileManager removeItemAtURL:error:] + 170
10 com.apple.AppKit 0x96ca63ca -[NSPersistentUIManager _interiorClearCrashCountFileIfNecessary] + 125
11 com.apple.AppKit 0x96ca6308 __-[NSPersistentUIManager modifyCrashBlameCounterBy:]_block_invoke_1 + 199
12 libdispatch.dylib 0x9b936fbd _dispatch_call_block_and_release + 15
13 libdispatch.dylib 0x9b938943 _dispatch_queue_drain + 224
14 libdispatch.dylib 0x9b9387e8 _dispatch_queue_invoke + 47
15 libdispatch.dylib 0x9b937ff0 _dispatch_worker_thread2 + 187
16 libsystem_c.dylib 0x94caab24 _pthread_wqthread + 346
17 libsystem_c.dylib 0x94cac6fe start_wqthread + 30
Thread 35:: Dispatch queue: com.apple.root.default-priority
0 libsystem_kernel.dylib 0x9af9883e __psynch_cvwait + 10
1 libsystem_c.dylib 0x94cace21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x94c5d42c pthread_cond_wait$UNIX2003 + 71
3 com.apple.Foundation 0x9b5e3768 -[__NSOperationInternal waitUntilFinished] + 145
4 com.apple.Foundation 0x9b5e36d0 -[NSOperation waitUntilFinished] + 67
5 com.apple.iPhoto 0x00255927 0x1000 + 2443559
6 com.apple.iPhoto 0x009e7d3b 0x1000 + 10382651
7 com.apple.Foundation 0x9b5ffe3a -[NSBlockOperation main] + 269
8 com.apple.Foundation 0x9b5c31cb -[__NSOperationInternal start] + 797
9 com.apple.Foundation 0x9b5c2ea7 -[NSOperation start] + 67
10 com.apple.Foundation 0x9b5d6ffa ____NSOQSchedule_block_invoke_2 + 135
11 libdispatch.dylib 0x9b936fbd _dispatch_call_block_and_release + 15
12 libdispatch.dylib 0x9b93801c _dispatch_worker_thread2 + 231
13 libsystem_c.dylib 0x94caab24 _pthread_wqthread + 346
14 libsystem_c.dylib 0x94cac6fe start_wqthread + 30
Thread 36:: Dispatch queue: CFPreferences Background Sync Queue
0 libsystem_kernel.dylib 0x9af9a272 stat$INODE64 + 10
1 com.apple.CoreFoundation 0x90150417 -[CFXPreferencesPropertyListSourceSynchronizer _backingPlistChangedSinceLastSync] + 103
2 com.apple.CoreFoundation 0x90150177 -[CFXPreferencesPropertyListSourceSynchronizer synchronizeAlreadyFlocked] + 39
3 com.apple.CoreFoundation 0x901500fa -[CFXPreferencesPropertyListSourceSynchronizer synchronize] + 522
4 com.apple.CoreFoundation 0x9019350a __-[CFXPreferencesPropertyListSource synchronizeInBackgroundWithCompletionBlock:]_block_invoke_1 + 122
5 libdispatch.dylib 0x9b936fbd _dispatch_call_block_and_release + 15
6 libdispatch.dylib 0x9b938943 _dispatch_queue_drain + 224
7 libdispatch.dylib 0x9b9387e8 _dispatch_queue_invoke + 47
8 libdispatch.dylib 0x9b937ff0 _dispatch_worker_thread2 + 187
9 libsystem_c.dylib 0x94caab24 _pthread_wqthread + 346
10 libsystem_c.dylib 0x94cac6fe start_wqthread + 30
Thread 37:: com.apple.NSURLConnectionLoader
0 libsystem_kernel.dylib 0x9af96c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9af961f6 mach_msg + 70
2 com.apple.CoreFoundation 0x901359da __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x9013eb04 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x9013e1dc CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x9013e088 CFRunLoopRunInMode + 120
6 com.apple.Foundation 0x9b5e20c4 +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 378
7 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
8 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
9 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
10 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 38:
0 libsystem_kernel.dylib 0x9af96c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9af961f6 mach_msg + 70
2 com.apple.iLifeSQLAccess 0x01860f41 -[RALatchTrigger wait] + 81
3 com.apple.iLifeSQLAccess 0x01860dc9 -[RAOperationQueueImpl _workThread] + 217
4 com.apple.Foundation 0x9b5d5e25 -[NSThread main] + 45
5 com.apple.Foundation 0x9b5d5dd5 __NSThread__main__ + 1582
6 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
7 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 39:: com.apple.CFSocket.private
0 libsystem_kernel.dylib 0x9af98b42 __select + 10
1 com.apple.CoreFoundation 0x9018ce15 __CFSocketManager + 1557
2 libsystem_c.dylib 0x94ca8ed9 _pthread_start + 335
3 libsystem_c.dylib 0x94cac6de thread_start + 34
Thread 40:
0 libsystem_kernel.dylib 0x9af9902e __workq_kernreturn + 10
1 libsystem_c.dylib 0x94caaccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x94cac6fe start_wqthread + 30
Thread 33 crashed with X86 Thread State (32-bit):
eax: 0x00010c2c ebx: 0x00008ca0 ecx: 0x00000018 edx: 0xfffff340
edi: 0x035be5f0 esi: 0x10e49c88 ebp: 0xb2b69728 esp: 0xb2b69720
ss: 0x00000023 efl: 0x00010282 eip: 0x94c80a91 cs: 0x0000001b
ds: 0x00000023 es: 0x00000023 fs: 0x00000023 gs: 0x0000000f
cr2: 0x10e49000
Logical CPU: 0
Binary Images:
0x1000 - 0xd28fe7 com.apple.iPhoto (9.2.2 - 9.2.2) <169B41B1-53E9-39E5-8154-43D2B0805600> /Applications/iPhoto.app/Contents/MacOS/iPhoto
0xe93000 - 0xf73fe7 org.python.python (2.6.7 - 2.6.7) <61DBA92A-C39A-3A52-86F2-59CF9D310CB4> /System/Library/Frameworks/Python.framework/Versions/2.6/Python
0xfbe000 - 0x115effb com.apple.geode (1.5.1 - 151.56) <96DB5B49-A0E9-31A6-B231-1342080D4982> /Applications/iPhoto.app/Contents/Frameworks/Geode.framework/Versions/A/Geode
0x11ff000 - 0x1201fff com.apple.iLifePhotoStreamConfiguration (2.2 - 2.2) <F5560FC9-1E0A-33E3-9BE0-439A30C5E0B4> /Applications/iPhoto.app/Contents/Frameworks/iLifePhotoStreamConfiguration.fram ework/Versions/A/iLifePhotoStreamConfiguration
0x1207000 - 0x1216ff7 com.apple.iLifeAssetManagement (2.1 - 10.12) <76BFFB15-42B6-360B-8662-4A8C3CE5625A> /Applications/iPhoto.app/Contents/Frameworks/iLifeAssetManagement.framework/Ver sions/A/iLifeAssetManagement
0x1223000 - 0x124bffb com.apple.iPhoto.Tessera (1.1 - 60.11) <4436A07F-C1C2-35EC-AE4E-1C78D2E5DB17> /Applications/iPhoto.apHey braswell4AU: I have a similar issue. I purchased 2 iPhone 5's the first day they came out. Black 64gb for myself and white 32gb for my wife. She is having somewhat the same issues as you have. Wifi is weak and keeps dropping the signal, and also her phone almost never has LTE. And we are in a very strong Verizon LTE area in north Los Angeles county. My phone has never had any signal issues, wifi or LTE. I have been researching the issue to no avail. I though maybe the white with the brushed alluminum may cause signal issues, but haven't found anything on that and posts about the black one haven't problems blew that theory up.
I have also changed the SIM card and the phone itself and still the same problem. I saw a post about someone getting their phone swapped out and the apple rep told him not to restore the phone, but to just set it up as new. I have yet to try it, gonna try this weekend.. But it makes sense! I, like you have 6 apple devices (2 iPhone 5's, 2 iPhone 4's apple tv3, and the ipad3) and have no issues running all my devices via router.
So I am thinking about the history of the restores and backups and my wife is the only one that went from the 4 to the 5.. Every other device was setup as new. So my theory is that he iphone 5 has issues when you restore from previous backups.. Maybe something a little different from the backups of the previous models create issues in the iPhone 5's?
Like I said, I'm going to give it a shot this weekend and see what happens. If you get a chance to try this before, please let me know if it works and if I try before you I will update you.
Good luck and hopefully we can get these wonderful phones working like they should!
Nate -
Worried about need to constantly repair disk permissions
Here is my analysis and conclusions as to why I need to constantly repair disk permissions:
I recently got the top-o'-the-line iMac (see info below) which shipped with Lion but since I wanted Snow Leopard (just because I have a few PowerPC games that I can't live without) I reformatted the hard drive - into 1 partition from the 2 that Lion had - and installed Snow Leopard and went back to business as usual....only with one **** great and fast computer. BTW, as far as I know this computer is exactly the same computer that shipped with Snow Leopard prior to Lion's introduction. I swore that I would never get another desktop computer because this one would last me forever. My only hesitation now is because the need to constantly repair permissions means something is not right. On the one hand I could just keep on repairing (daily?) the permissions for the next 20 years, or.... what? Is it possible (or should I be asking Apple itself instead of in this forum) that there is some other difference between the Snow Leopard and the Lion versions of this iMac - is this what "firmware" is all about? - that produces this constant need to repair permissions? If that's the case, would Apple give me a Snow Leopard-friendly logic board (and/or install the correct firmware) in exchange for the Lion logic board - or am I just going to have to live with having to perform this permissions-update function? Or is having to repair disk permissions not a big deal or something worrying about? Any ideas would be appreciated - thanks!
Hardware Overview:
Model Name: iMac
Model Identifier: iMac12,2
Processor Name: Intel Core i7
Processor Speed: 3.4 GHz
Number Of Processors: 1
Total Number Of Cores: 4
L2 Cache (per core): 256 KB
L3 Cache: 8 MB
Memory: 12 GB
Boot ROM Version: IM121.0047.B0A
SMC Version (system): 1.72f2
Hardware UUID: B9D5A82D-6205-5FDD-BE77-46CC72811374You do not need to repair permissions unless there's a specific problem.
For your info;
http://support.apple.com/kb/TS1448
Maybe you are looking for
-
Acrobat Pro 9.4.4 occasionally prints web pages as garbage
Hello All, When I'm on a secure site like online banking, when I try to print a confirmation page it sometimes prints the DATA out as special characters, etc. Even using the page's "Print" command doesn't help. I'm not sure if this coincides with a
-
Error after schudling report for triggring proxy
Hi friends, In the scnario proxy-jdbc.. i have moved the interface to production and schudled the abap report in background jobs. now when the report is triggered the proxy is called and here i am getting this error. INTERNAL.CLIENT_RECEIVE_FAILED Er
-
My address bar won't stay open.
I just installed the new firefox and now my address bar won't stay open. My husband who just installed it has no problems. How do i fix this?
-
I have a new MBP with Mavericks 10.9 and a 250GB SSD. i am new to Mac and like and idoit I tried to change the name of my hard drive in Macintosh HD. I then changed it back to original name. When starting it up again I got the disc utlity repair as
-
Merlin checks the Mac: Script Will work in XP & Vista 32 & 64, from Microsoft's "Scripting Guy" sample. Merlin character knocks on your monitor from the inside then proceeds to check out your Mac. Flies about for a bit and exits by dissappearing into