Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Maybe. My theory is that it is related to on-device processing of photos for face and object recognition, so turning off iCloud Photos will probably not prevent that happening if you have already downloaded them to the phone.

I'd be very surprised indeed if the crashing was related to a simple network operation like uploading or downloading photos - complex processing is a far more likely culprit.
So in theory if I don’t take any pics for a few days it may not happen?
 
  • Like
Reactions: scapegoat81
Two different iPhone 14PM within the same household are restarting when using the Eufy app. None are on iOS beta.

My panic string is:

panicString" : "panic(cpu 1 caller 0xfffffff01d03eeb8): \"dart-avd (0xffffffe603925000): DART(DART) error: SID 0 CTE invalid exception on read of DVA 0 (CTE 0 SEG 0 PTE 0) ERROR_STATUS 0x80080002 TIME 0xec931614e6 TTE 0xffffffffffffffff AXI_ID 0x300\"
same string as mine!

I think it is highly correlated with iCloud backup process. it appears when I backup my phone to iCloud manually, or changing and connecting with wifi at night.
 
  • Like
Reactions: Fred Zed
same string as mine!

I think it is highly correlated with iCloud backup process. it appears when I backup my phone to iCloud manually, or changing and connecting with wifi at night.
I think you’re on to something. My last successful backup was 12:11. The status app showed my phone rebooted 12:12 am on charger. Sounds more and more like software.
 
  • Like
Reactions: scapegoat81
Latest crash logs from mine - it crashes spontaneously while locked connected to power - the exact conditions necessary for iCloud Photo processing to occur.
 

Attachments

  • latest crashes.zip
    204.8 KB · Views: 84
It's been over 24 hours and not a single crash - after I disabled iCloud photos.

Context: I had about 85GB of photos from my 13 Pro. Restored iCloud backup to 14 Pro. Realized I have tons of space in iCloud, so I enabled iCloud photos - and it was crashing very often.
 
  • Like
Reactions: scapegoat81
It's been over 24 hours and not a single crash - after I disabled iCloud photos.

Context: I had about 85GB of photos from my 13 Pro. Restored iCloud backup to 14 Pro. Realized I have tons of space in iCloud, so I enabled iCloud photos - and it was crashing very often.

A few debugging questions:

1. How many photos are now stored on your 14 Pro (quantity and data size)?

2. Assuming you have photo content, what do you see if you view Photos > Albums > People & Places > People? Do you see a countdown of photos remaining to be processed?

photo analysis progress.jpeg


My current theory is that photo analysis of certain photo data is killing the A16 as it tries to process photos the phone hasn't previously analysed.

In my case, it started to crash (this time around) after it has gone through about 50,000 photos.

I'm just hoping that it doesn't enter the 14 Pro reboot loop of death again once it finishes or reaches a particular threshold.
 
About 3,000 photos, 280 videos. 52GB.

Yes I have people in my People folder. It hasn't finished yet, still updating it says.

Side tangent: Every couple years I delete all photos from my iphone if it grows too large. My main repository of photos is my Mac where all are sync'd via lightning cable. 224GB, 37k photos going all the way back to year 2000 with my Kodak DC280 2 megapixel digital camera lol. This massive library is definitely not in iCloud photos.
 
  • Like
Reactions: scapegoat81
About 3,000 photos, 280 videos. 52GB.

Yes I have people in my People folder. It hasn't finished yet, still updating it says.

Side tangent: Every couple years I delete all photos from my iphone if it grows too large. My main repository of photos is my Mac where all are sync'd via lightning cable. 224GB, 37k photos going all the way back to year 2000 with my Kodak DC280 2 megapixel digital camera lol. This massive library is definitely not in iCloud photos.
How does one manage a to people folder to sync correctly? I have 21000 photos but it only shows a dozen photos for said people.
 
I've noticed something else.

When the phone crashes and gets back to the initial Lock Screen, it won't crash again unless it's been unlocked.

This suggests that whatever is causing the crash doesn't operate at startup but waits for the initial phone unlock before it will start doing its thing.

Two crashes for me during the night - I unlocked it after the first one, hence the second crash later in the night. I didn't unlock it again until just now. I'm attaching the error logs just in case someone who can decipher them is hanging around here, but it's notable that there are two entries for cloudphotod, mentioning disk writes and cpu resources.

photoanalysisd.cpu_resource-2022-09-28-021054.ips
JSON:
{"duration_ms":"123105","share_with_app_devs":0,"roots_installed":0,"bug_type":"202","os_version":"iPhone OS 16.0.2 (20A380)","slice_uuid":"0471EEAA-1454-341B-8F59-7B87DF7EA46D","is_first_party":0,"incident_id":"4D33D7DF-4FEA-4755-896A-128216753A61","timestamp":"2022-09-28 02:10:54.00 +0100","app_name":"photoanalysisd","name":"photoanalysisd"}
Date/Time:        2022-09-28 02:08:50.699 +0100
End time:         2022-09-28 02:10:53.804 +0100
OS Version:       iPhone OS 16.0.2 (Build 20A380)
Architecture:     arm64e
Report Version:   40
Incident Identifier: 4D33D7DF-4FEA-4755-896A-128216753A61

Data Source:      Microstackshots
Shared Cache:     878A8CA2-7334-3BC2-A4C8-FF6069D46CC1 slid base address 0x1c85b8000, slide 0x485b8000

Command:          photoanalysisd
Path:             /System/Library/PrivateFrameworks/PhotoAnalysis.framework/Support/photoanalysisd
Resource Coalition ID: 491
Architecture:     arm64e
Parent:           UNKNOWN [1]
PID:              328

Event:            cpu usage
Action taken:     none
CPU:              90 seconds cpu time over 123 seconds (73% cpu average), exceeding limit of 50% cpu over 180 seconds
CPU limit:        90s
Limit duration:   180s
CPU used:         90s
CPU duration:     123s
Duration:         123.11s
Duration Sampled: 122.46s
Steps:            151

Hardware model:   iPhone15,2
Active cpus:      6
HW page size:     16384
VM page size:     16384
photoanalysisd.diskwrites_resource-2022-09-28-021554.ips
JSON:
{"duration_ms":"1271068","share_with_app_devs":0,"roots_installed":0,"bug_type":"145","os_version":"iPhone OS 16.0.2 (20A380)","slice_uuid":"0471EEAA-1454-341B-8F59-7B87DF7EA46D","is_first_party":0,"incident_id":"5C35F59A-76F2-4EF4-9EDF-F4DE1F0A7D26","timestamp":"2022-09-28 02:15:54.00 +0100","app_name":"photoanalysisd","name":"photoanalysisd"}
Date/Time:        2022-09-28 01:54:41.464 +0100
End time:         2022-09-28 02:15:52.532 +0100
OS Version:       iPhone OS 16.0.2 (Build 20A380)
Architecture:     arm64e
Report Version:   40
Incident Identifier: 5C35F59A-76F2-4EF4-9EDF-F4DE1F0A7D26

Data Source:      Microstackshots
Shared Cache:     878A8CA2-7334-3BC2-A4C8-FF6069D46CC1 slid base address 0x1c85b8000, slide 0x485b8000

Command:          photoanalysisd
Path:             /System/Library/PrivateFrameworks/PhotoAnalysis.framework/Support/photoanalysisd
Resource Coalition ID: 491
Architecture:     arm64e
Parent:           launchd [1]
PID:              328

Event:            disk writes
Action taken:     none
Writes:           1073.75 MB of file backed memory dirtied over 1271 seconds (844.76 KB per second average), exceeding limit of 12.43 KB per second over 86400 seconds
Writes limit:     1073.74 MB
Limit duration:   86400s
Writes caused:    1073.75 MB
Writes duration:  1271s
Duration:         1271.07s
Duration Sampled: 1260.05s
Steps:            1454 (10.49 MB/step)

Hardware model:   iPhone15,2
Active cpus:      6
HW page size:     16384
VM page size:     16384
 

Attachments

  • error logs night time 2022-09-28.zip
    387.9 KB · Views: 70
I've noticed something else.

When the phone crashes and gets back to the initial Lock Screen, it won't crash again unless it's been unlocked.

This suggests that whatever is causing the crash doesn't operate at startup but waits for the initial phone unlock before it will start doing its thing.

Two crashes for me during the night - I unlocked it after the first one, hence the second crash later in the night. I didn't unlock it again until just now. I'm attaching the error logs just in case someone who can decipher them is hanging around here, but it's notable that there are two entries for cloudphotod, mentioning disk writes and cpu resources.

photoanalysisd.cpu_resource-2022-09-28-021054.ips
JSON:
{"duration_ms":"123105","share_with_app_devs":0,"roots_installed":0,"bug_type":"202","os_version":"iPhone OS 16.0.2 (20A380)","slice_uuid":"0471EEAA-1454-341B-8F59-7B87DF7EA46D","is_first_party":0,"incident_id":"4D33D7DF-4FEA-4755-896A-128216753A61","timestamp":"2022-09-28 02:10:54.00 +0100","app_name":"photoanalysisd","name":"photoanalysisd"}
Date/Time:        2022-09-28 02:08:50.699 +0100
End time:         2022-09-28 02:10:53.804 +0100
OS Version:       iPhone OS 16.0.2 (Build 20A380)
Architecture:     arm64e
Report Version:   40
Incident Identifier: 4D33D7DF-4FEA-4755-896A-128216753A61

Data Source:      Microstackshots
Shared Cache:     878A8CA2-7334-3BC2-A4C8-FF6069D46CC1 slid base address 0x1c85b8000, slide 0x485b8000

Command:          photoanalysisd
Path:             /System/Library/PrivateFrameworks/PhotoAnalysis.framework/Support/photoanalysisd
Resource Coalition ID: 491
Architecture:     arm64e
Parent:           UNKNOWN [1]
PID:              328

Event:            cpu usage
Action taken:     none
CPU:              90 seconds cpu time over 123 seconds (73% cpu average), exceeding limit of 50% cpu over 180 seconds
CPU limit:        90s
Limit duration:   180s
CPU used:         90s
CPU duration:     123s
Duration:         123.11s
Duration Sampled: 122.46s
Steps:            151

Hardware model:   iPhone15,2
Active cpus:      6
HW page size:     16384
VM page size:     16384
photoanalysisd.diskwrites_resource-2022-09-28-021554.ips
JSON:
{"duration_ms":"1271068","share_with_app_devs":0,"roots_installed":0,"bug_type":"145","os_version":"iPhone OS 16.0.2 (20A380)","slice_uuid":"0471EEAA-1454-341B-8F59-7B87DF7EA46D","is_first_party":0,"incident_id":"5C35F59A-76F2-4EF4-9EDF-F4DE1F0A7D26","timestamp":"2022-09-28 02:15:54.00 +0100","app_name":"photoanalysisd","name":"photoanalysisd"}
Date/Time:        2022-09-28 01:54:41.464 +0100
End time:         2022-09-28 02:15:52.532 +0100
OS Version:       iPhone OS 16.0.2 (Build 20A380)
Architecture:     arm64e
Report Version:   40
Incident Identifier: 5C35F59A-76F2-4EF4-9EDF-F4DE1F0A7D26

Data Source:      Microstackshots
Shared Cache:     878A8CA2-7334-3BC2-A4C8-FF6069D46CC1 slid base address 0x1c85b8000, slide 0x485b8000

Command:          photoanalysisd
Path:             /System/Library/PrivateFrameworks/PhotoAnalysis.framework/Support/photoanalysisd
Resource Coalition ID: 491
Architecture:     arm64e
Parent:           launchd [1]
PID:              328

Event:            disk writes
Action taken:     none
Writes:           1073.75 MB of file backed memory dirtied over 1271 seconds (844.76 KB per second average), exceeding limit of 12.43 KB per second over 86400 seconds
Writes limit:     1073.74 MB
Limit duration:   86400s
Writes caused:    1073.75 MB
Writes duration:  1271s
Duration:         1271.07s
Duration Sampled: 1260.05s
Steps:            1454 (10.49 MB/step)

Hardware model:   iPhone15,2
Active cpus:      6
HW page size:     16384
VM page size:     16384
I think this one "photoanalysisd.cpu_resource-2022-09-28-021054.ips" was generated while the photoanalysisd process was killed due to CPU over load in the background, as stated here "90 seconds cpu time over 123 seconds (73% cpu average), exceeding limit of 50% cpu over 180 seconds".

The logs recording the reboot(panic) of the phone should be those starting with "panic-full-xxxx", which is hard to decipher unless there's someone familiar with apple system kernel stuff.
Please let there be such ppl hanging around here. 😂
 
A few miscellaneous notes:
  • Tech vlogs are starting to take notice of this issue.
  • Turning off background app refresh is the first thing I do when I set up a phone as new. I was most certainly seeing the restarts happen with background refresh deactivated.
  • Unless it takes more than a week for iCloud to synchronize photos, that's not it either. My phone sits on the charger overnight every night. I had restarts every night from 9/16 when I received the phone until 9/26 when I sent it back to Apple.
  • For what it's worth, this is my log of restarts. During this period, I tried 16.0.1, 16.0.2, phone-to-phone setup, setup from tethered restore, and setup as new phone:
9/16/22, Friday, crashed/restarted on charger, 10:41pm
9/17/22, Saturday, crashed/restarted on charger, 9:52pm
9/18/22, Sunday, crashed/restarted on charger, 10:15pm
9/19/22, Monday, crashed/restarted on charger, 9:59pm
9/20/22, Tuesday, crashed/restarted on charger, 10:18pm
9/21/22, Wednesday, crashed/restarted on charger, 10:05pm
9/22/22, Thursday, crashed/restarted on charger, 10:32pm
9/23/22, Friday, crashed/restarted on charger, 11:18pm
9/24/22, Saturday, crashed/restarted on charger, 10:32am
9/24/22, Saturday, crashed/restarted on charger, 11:24am *
(* This is when I noticed the problem as it happened right in front of me.)
9/24/22, Saturday, crashed/restarted during tethered backup, 11:50am
9/24/22, Saturday, crashed/restarted during tethered backup, 11:58am
9/25/22, Sunday, crashed/restarted on charger, 2:24am
9/26/22, Monday, crashed on/restarted charger, 5:20am
 
  • Like
Reactions: scapegoat81
A few miscellaneous notes:
  • Tech vlogs are starting to take notice of this issue.
  • Turning off background app refresh is the first thing I do when I set up a phone as new. I was most certainly seeing the restarts happen with background refresh deactivated.
  • Unless it takes more than a week for iCloud to synchronize photos, that's not it either. My phone sits on the charger overnight every night. I had restarts every night from 9/16 when I received the phone until 9/26 when I sent it back to Apple.
Background app refresh
It's not actually possible to disable background processing - the option does not appear under the background app refresh preference pane, so turning off background app refresh potentially has no bearing on this problem

Photos sync / analysis
In my case, syncing iCloud photos takes 2-3 days over a gigabit Internet connection. Only after this sync will photo analysis begin
 
I am on a 14PM, no reboots, but I did have issues with my previous qi charger not playing nice with my phone, taking at least 4 resets on the charging cradle before it'd stop hiccuping. Got a magsafe charger and the problem went away for me. No panics for my phone, no random resets. My suspicion lays in defective hardware or a bad restore for the panic folk.
 
  • Like
Reactions: scapegoat81
A bad (corrupted on the icloud server maybe?) restore is possible, as soon as I turned off iCloud photos it completely stopped crashing. So if it was trying to upload a corrupted file, or the photo library on my phone itself is corrupted, it reaches that point in the icloud photo upload process and it hangs.
 
Mine crashes almost every time I charge it. Just crashes twice in the last twenty minutes. I don’t have iCloud photo backup turned on and never have. I have iCloud backup on but not photos. And it just crashes with a panic twice and the iCloud backup hasn’t kicked off.
 
Mine crashes almost every time I charge it. Just crashes twice in the last twenty minutes. I don’t have iCloud photo backup turned on and never have. I have iCloud backup on but not photos. And it just crashes with a panic twice and the iCloud backup hasn’t kicked off.
Please report it to Apple support - you can do it right over the phone
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.