Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

x-evil-x

macrumors 603
Original poster
Jul 13, 2008
5,621
3,304
My springboard crashed today and I'm trying to figure out what was the reason. I was on Facebook and phone crashed. How do I read it? My ram was around 85% used at the time.
 

Attachments

  • image.jpg
    image.jpg
    66.5 KB · Views: 775
My springboard crashed today and I'm trying to figure out what was the reason. I was on Facebook and phone crashed. How do I read it? My ram was around 85% used at the time.

Man I wish I knew how to decipher those. I think you need to have an understanding of debugging to figure it out. I've spent many hours googling this topic and never really got anywhere.

When you tap on Facebook, does crash reporter list any "suspects"? Usually if it can give you that information, sometimes that points you in the right direction. But I've had times when it said one thing was the main suspect but it ended up being something completely different. I stopped using crash reporter unless a dev asks me for a log. Now I do it the manual way...disable tweaks one at a time to find the problem. Sometimes though, apps from the App Store have crashing issues. Not sure if Facebook is one of them though. I don't use Facebook.

I'm gonna keep my eye on this thread though in case someone posts some type of beginners guide to deciphering crash logs. If love to learn more about this.

Edit: if you search/look through the first 3-5 pages of threads, you'll see numerous threads that discuss the Facebook app crashing. You can probably find some helpful information in those threads. Good luck. Wish I knew more.
 
Last edited:
Thanks for the long response most people on here just tell others to search and don't help anybody out.
I need to figure out what's causing it. I do have copic(pictures for contacts and messages). That one is crashing the SMS app. Hopefully they update that I don't know if that would have anything with the springboard crashing.
I also have dock( side app switcher) with activator.
For the Facebook one it doesn't have any culprits for suspected crashes. So I'm not sure.
Does the springboard crash if the ram is very high? Never had this problem stock.
 
Thanks for the long response most people on here just tell others to search and don't help anybody out.
I need to figure out what's causing it. I do have copic(pictures for contacts and messages). That one is crashing the SMS app. Hopefully they update that I don't know if that would have anything with the springboard crashing.
I also have dock( side app switcher) with activator.
For the Facebook one it doesn't have any culprits for suspected crashes. So I'm not sure.
Does the springboard crash if the ram is very high? Never had this problem stock.

Not sure about all your problems. I don't have any crashes or anything like that on my device but at the same time I don't have a ton of stuff installed. And pretty much all my installed packages are from the most well known and well respected devs on Cydia.

But I can tell you that low ram usually doesn't (can't?) crash the springboard. If anything it will cause an app to crash. My guess is that one of your packages is causing springboard to crash. Try going through them one by one disabling them until the problem goes away. Once it stops, odds are that tweak is the problem.

If/when you find out what's causing the crashes please post that information here so others will be aware of it too. Good luck!
 
Thanks for the long response most people on here just tell others to search and don't help anybody out.
I need to figure out what's causing it. I do have copic(pictures for contacts and messages). That one is crashing the SMS app. Hopefully they update that I don't know if that would have anything with the springboard crashing.
I also have dock( side app switcher) with activator.
For the Facebook one it doesn't have any culprits for suspected crashes. So I'm not sure.
Does the springboard crash if the ram is very high? Never had this problem stock.

What tweaks do you have installed? We might be able to point out tweaks with known bugs...
 
I'll be another one to add that the FB app is buggy as hell. I watched it crash on my husband's completely stock, never been JB'd iPad several times this afternoon.

Atomic Browser is also crashing to Springboard almost every time I download a file. Since that's my usual go-to app for downloading widgets, icons, and the like, it's been pretty irritating the last two weeks.

But in that instance, I have an easily replicated situation: Too many apps in the switcher, too many open processes. Kill all background apps, and it will *usually* behave. Nothing fixes Facebook, and most likely nothing will until they update the app.

I'd love to see someone chime in on how to read these reports. Unless they list a suspect, I have no clue what they mean, and I'd like to be able to triage more of this stuff myself.
 
Coming from an OSX standpoint, it's always helpful if you post the entire crash log. You'll want a fresh one, i.e., one from when it just crashed. Crash logs tend to be long so if you post it, it'll probably be a long post.

I don't read crash log, but I know people (engineers) who do and the little I've picked up from them can help decipher things somewhat.

Apps process things in threads. The crash log will tell you which thread crashed and may offer some reason as to why. High memory use in and of itself won't crash an app, but if an app is asking for memory that isn't there because of a low memory state that could force the app to crash.

Typically, crashes are because apps ask for something that either they aren't allowed to have or that isn't available (such as more memory when it's not there). But we won't know unless we see the actual crash log.
 
Interesting stuff!

Here's a follow on question: why do some crashes to Springboard not generate logs? Going back to Facebook as an example, I have exactly one crash report, yet I know it's sent me back to the Springboard at least 4-5x a week. (This is why I stopped even looking at them on my iPad; no real point since there wasn't any data to work with at all.)
 
Well, if it was FB crashing you'd look for the FB crash log, not the Springboard. Even if FB took out the Springboard the original crash was from FB so that's the log you'd look at.

Sometimes it does happen so fast though that a log doesn't get written, or only partially written.

Here's a log from my most recent crash of FB. This was due to Copic, which had two updates that day (Friday the 8th). I know that because Copic was crashing when I was scrolling in AddressBook. Then I opened FB and it crashed right away. If you look at the first few lines of the log it's pretty evident that it crashed trying to access my contacts when the FB app was opening. Again, I don't read crash log, but some stuff jumps out at you when you put things in context.

Version:1.0 StartHTML:0000000149 EndHTML:0000005585 StartFragment:0000000199 EndFragment:0000005551 StartSelection:0000000199 EndSelection:0000005551 Incident Identifier: EEEAC4F9-7E2D-4C04-A32A-992221BCCDA4
CrashReporter Key: adb1cd2cfec7194db6c1a4ed65389ef1f5a89609
Report Type: 187
Sandbox Violation: Facebook deny file-read-metadata /private/var/mobile/Library/AddressBook/AddressBook.sqlitedb

Process: Facebook [537]
Path: /var/mobile/Applications/E814C6E2-DAEC-4086-93B4-74D0C30ADEE2/Facebook.app/Facebook
Load Address: 0xb2000
Identifier: Facebook
Version: ??? (???)
Code Type: arm (Native)
Parent Process: launchd [1]

Date/Time: 2013-03-08 23:24:46.697 -0700
OS Version: iOS 6.1 (10B143)
Report Version: 104

Thread 0:
0 libsystem_kernel.dylib 0x39346f28 lstat + 8
1 Foundation 0x319de7e1 _NSFileExistsAtPath + 181
2 Foundation 0x319e79d1 -[NSFileManager fileExistsAtPath:isDirectory:] + 117
3 xCon.dylib 0x025f5aef _logos_method$NSFileManager$NSFileManager$fileExistsAtPath$isDirectory$(NSFileManager*, objc_selector*, NSString*, signed char*) + 23
4 Copic.dylib 0x022c62f4
5 Copic.dylib 0x022c6588
6 CoreFoundation 0x3113e0a5 __CFNotificationCenterAddObserver_block_invoke_0 + 125
7 CoreFoundation 0x3113e1bb ____CFXNotificationPostToken_block_invoke_0 + 143
8 CoreFoundation 0x31146925 __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 13
9 CoreFoundation 0x31145ff9 __CFRunLoopDoBlocks + 161
10 CoreFoundation 0x31145253 __CFRunLoopRun + 1451
11 CoreFoundation 0x310b823d CFRunLoopRunSpecific + 357
12 CoreFoundation 0x310b80c9 CFRunLoopRunInMode + 105
13 GraphicsServices 0x34c9633b GSEventRunModal + 75
14 UIKit 0x32fd42b9 UIApplicationMain + 1121
15 Facebook 0x000b4bd5
16 Facebook 0x000b4b98

Binary Images:
0xb2000 - 0xb1affd Facebook armv7 <7cab8d7bacec344d970a03050649a1f3> /var/mobile/Applications/E814C6E2-DAEC-4086-93B4-74D0C30ADEE2/Facebook.app/Facebook
0x22b8000 - 0x22dcffb Copic.dylib armv6 <b444d22eb8b53203a24936ac275ef2fd> /Library/MobileSubstrate/DynamicLibraries/Copic.dylib
0x25f2000 - 0x25f7fff xCon.dylib armv7 <83b67a1c646f316d8bc3305de9fafd64> /Library/MobileSubstrate/DynamicLibraries/xCon.dylib
0x310af000 - 0x311e1ff1 CoreFoundation armv7s <bd8e6c9f94b43e3d9af96a0f03ff3011> /System/Library/Frameworks/CoreFoundation.framework/CoreFoundation
0x319d8000 - 0x31b9bffd Foundation armv7s <0f73c35ada563c0bb2ce402d282faefd> /System/Library/Frameworks/Foundation.framework/Foundation
0x32f7d000 - 0x334d0ff3 UIKit armv7s <62bee9294ca13738bd7ff14365dc8561> /System/Library/Frameworks/UIKit.framework/UIKit
0x34c91000 - 0x34c9cfff GraphicsServices armv7s <44b33c403523309c9e930818c7fced34> /System/Library/PrivateFrameworks/GraphicsServices.framework/GraphicsServices
0x39345000 - 0x3935bffd libsystem_kernel.dylib armv7s <79bea3ebfda132baba8f5b0ad6ab95f5> /usr/lib/system/libsystem_kernel.dylib
 
What tweaks do you have installed? We might be able to point out tweaks with known bugs...

heres a list of installed apps. some of these things get added with other apps as i didnt instal them.



Cydia™ user sources:
1. http://patrickmuff.ch/repo/ ./


List of installed packages:
0. 7-zip (POSIX)
1. AppList
2. APR (/usr/lib)
3. APT 0.6 Transitional
4. APT 0.7 (apt-key)
5. APT 0.7 HTTPS Method
6. APT 0.7 Strict
7. APT 0.7 Strict (lib)
8. Auxo
9. basic-cmds
10. Berkeley DB
11. BigBoss Icon Set
12. Blackout
13. Blackout
14. Bourne-Again SHell
15. bzip2
16. Climacons iWidget
17. Color Keyboard
18. colorflow Lockscreen
19. Copic
20. Core Utilities
21. Core Utilities (/bin)
22. Crash Reporter
23. cURL
24. Darwin Tools
25. Debian Packager
26. Debian Utilities
27. Diff Utilities
28. diskdev-cmds
29. Erica Utilities
30. evasi0n 6.0-6.1.2 Untether
31. é&#135;&#145;å±±ç&#148;µæ± å&#140;»ç&#148;&#159;ä¸&#147;ä¸&#154;ç&#137;&#136;(BatteryDoctorPro)
32. file-cmds
33. Find Utilities
34. FolderEnhancer
35. Gawk
36. gettext
37. GNU Privacy Guard
38. grep
39. Gridlock 2.0
40. gzip
41. iCleaner
42. IconSupport
43. iFile
44. iMatte v5 ColorKeyboard Theme
45. IntelliScreenX (iOS 6 Library)
46. IntelliScreenX 6
47. iWidgets
48. LayerSnapshotter
49. less
50. libhide
51. libstatusbar
52. LZMA Utils
53. Mobile Substrate
54. network-cmds
55. New Curses
56. OpenSSL
57. PAM (Apple)
58. PAM Modules
59. pcre
60. PdaNet
61. pincrush
62. PreferenceLoader
63. Profile Directory
64. readline
65. Remove WallGradient
66. RisingBars Lockscreen
67. sed
68. shell-cmds
69. Springtomize 2 - iOS 5 & 6
70. Springtomize2-Icons
71. Springtomize2-Localizations
72. Substrate Safe Mode
73. symbolicate
74. syslogd to /var/log/syslog
75. system-cmds
76. Tape Archive
77. UIKit Tools
78. unrar
79. WeeLoader
80. WinterBoard
81. Zephyr
82. Zeppelin
 
Well, if it was FB crashing you'd look for the FB crash log, not the Springboard. Even if FB took out the Springboard the original crash was from FB so that's the log you'd look at.

Sometimes it does happen so fast though that a log doesn't get written, or only partially written.

Here's a log from my most recent crash of FB. This was due to Copic, which had two updates that day (Friday the 8th). I know that because Copic was crashing when I was scrolling in AddressBook. Then I opened FB and it crashed right away. If you look at the first few lines of the log it's pretty evident that it crashed trying to access my contacts when the FB app was opening. Again, I don't read crash log, but some stuff jumps out at you when you put things in context.

Version:1.0 StartHTML:0000000149 EndHTML:0000005585 StartFragment:0000000199 EndFragment:0000005551 StartSelection:0000000199 EndSelection:0000005551 Incident Identifier: EEEAC4F9-7E2D-4C04-A32A-992221BCCDA4
CrashReporter Key: adb1cd2cfec7194db6c1a4ed65389ef1f5a89609
Report Type: 187
Sandbox Violation: Facebook deny file-read-metadata /private/var/mobile/Library/AddressBook/AddressBook.sqlitedb

Process: Facebook [537]
Path: /var/mobile/Applications/E814C6E2-DAEC-4086-93B4-74D0C30ADEE2/Facebook.app/Facebook
Load Address: 0xb2000
Identifier: Facebook
Version: ??? (???)
Code Type: arm (Native)
Parent Process: launchd [1]

Date/Time: 2013-03-08 23:24:46.697 -0700
OS Version: iOS 6.1 (10B143)
Report Version: 104

Thread 0:
0 libsystem_kernel.dylib 0x39346f28 lstat + 8
1 Foundation 0x319de7e1 _NSFileExistsAtPath + 181
2 Foundation 0x319e79d1 -[NSFileManager fileExistsAtPath:isDirectory:] + 117
3 xCon.dylib 0x025f5aef _logos_method$NSFileManager$NSFileManager$fileExistsAtPath$isDirectory$(NSFileManager*, objc_selector*, NSString*, signed char*) + 23
4 Copic.dylib 0x022c62f4
5 Copic.dylib 0x022c6588
6 CoreFoundation 0x3113e0a5 __CFNotificationCenterAddObserver_block_invoke_0 + 125
7 CoreFoundation 0x3113e1bb ____CFXNotificationPostToken_block_invoke_0 + 143
8 CoreFoundation 0x31146925 __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 13
9 CoreFoundation 0x31145ff9 __CFRunLoopDoBlocks + 161
10 CoreFoundation 0x31145253 __CFRunLoopRun + 1451
11 CoreFoundation 0x310b823d CFRunLoopRunSpecific + 357
12 CoreFoundation 0x310b80c9 CFRunLoopRunInMode + 105
13 GraphicsServices 0x34c9633b GSEventRunModal + 75
14 UIKit 0x32fd42b9 UIApplicationMain + 1121
15 Facebook 0x000b4bd5
16 Facebook 0x000b4b98

Binary Images:
0xb2000 - 0xb1affd Facebook armv7 <7cab8d7bacec344d970a03050649a1f3> /var/mobile/Applications/E814C6E2-DAEC-4086-93B4-74D0C30ADEE2/Facebook.app/Facebook
0x22b8000 - 0x22dcffb Copic.dylib armv6 <b444d22eb8b53203a24936ac275ef2fd> /Library/MobileSubstrate/DynamicLibraries/Copic.dylib
0x25f2000 - 0x25f7fff xCon.dylib armv7 <83b67a1c646f316d8bc3305de9fafd64> /Library/MobileSubstrate/DynamicLibraries/xCon.dylib
0x310af000 - 0x311e1ff1 CoreFoundation armv7s <bd8e6c9f94b43e3d9af96a0f03ff3011> /System/Library/Frameworks/CoreFoundation.framework/CoreFoundation
0x319d8000 - 0x31b9bffd Foundation armv7s <0f73c35ada563c0bb2ce402d282faefd> /System/Library/Frameworks/Foundation.framework/Foundation
0x32f7d000 - 0x334d0ff3 UIKit armv7s <62bee9294ca13738bd7ff14365dc8561> /System/Library/Frameworks/UIKit.framework/UIKit
0x34c91000 - 0x34c9cfff GraphicsServices armv7s <44b33c403523309c9e930818c7fced34> /System/Library/PrivateFrameworks/GraphicsServices.framework/GraphicsServices
0x39345000 - 0x3935bffd libsystem_kernel.dylib armv7s <79bea3ebfda132baba8f5b0ad6ab95f5> /usr/lib/system/libsystem_kernel.dylib

ive sent an email to the copic developers explaining the problems its having. Let me know if you have this problem too.
When you first open messages app clean it will crash. sometimes it will crash 2-3 times before its fine. It shows one person for the whole list for a second then crashes.
Also in contacts app it will flash/black for a split second and then be ok.(having trouble reproducing now).
hopefully they come out with a fix soon
 
Have you checked Cydia for updates? There were two on Friday the 8th. I suppose to address the issue. I have Copic so I experienced the exact same thing you did.
 
i thought i did update it. im still having problems with the sms issue i said.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.