Respring on iPad3 iOS 7.0.4
Hello everybody, I hope this can be of any help: This respring issue has happened on mi iPad3 for about a month now. It started while using a specific App I use [rather frequently] for reading and annotating, therefore I strongly believe it is related to memory usage (perhaps GPU?) since I often load a full library of hefty .pdfs such as books on that app. It has not happened while using Safari, Netflix, Youtube or any other video app, unlike many of you, not even while swiping and despite dozens of tabs in Safari. I'm using iOS 7.0.4 and this started happening this year. Since I've had the iPad for more than two years now, I'd say it has to with iOS 7; I ran a previous version of that same app on iOS6 last year and it ran smoothly, never crashed. When I adressed the app's CS dept they referred me to this thread and said themselves it had to do with iOS. The # of times it resprings depends usually on how long I use the app or the processes that occur within the app, but on a busy day it can easily happen +5 times. Here r some frags of the reports:
Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x00000008
Triggered by Thread:  12
Thread 12 Crashed:
0 CoreGraphics 0x308bf3b0 0x30819000 + 680880
1 CoreGraphics 0x308ae306 0x30819000 + 611078
2 CoreGraphics 0x3090aac2 0x30819000 + 989890
3 CoreGraphics 0x308e9bbc 0x30819000 + 854972 (and goes on...)
here's another crash report triggered by the same app:
Exception Type:  EXC_CRASH (SIGABRT)
Exception Code: 0x0000000000000000, 0x0000000000000000
Triggered by Thread:  12
Thread 12 Crashed:
0   libsystem_kernel.dylib        	0x3b5dfc7c 0x3b5cc000 + 81020
1   libsystem_pthread.dylib       	0x3b645dc6 0x3b645000 + 3526
2   libsystem_pthread.dylib       	0x3b645c80 0x3b645000 + 3200
Thread 12 crashed with ARM Thread State (32-bit):
    r0: 0x00000004    r1: 0x00000000      r2: 0x00000000      r3: 0x00000000
    r4: 0x03f66000    r5: 0x00070001      r6: 0x00003187      r7: 0x03f65fe0
    r8: 0x00000001    r9: 0x166c07a0     r10: 0x00000000     r11: 0x00000000
    ip: 0x00000170    sp: 0x03f65fc8      lr: 0x3b645dcb      pc: 0x3b5dfc7c
  cpsr: 0x40000010
Curiously enough, the other [in my opinion] memory intensive app I've used recently is Microsoft Lync, on which I held a 2h conference call (A/V). Report: 
Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000102, 0x000000009cd08582
Triggered by Thread:  0
Thread 0 Crashed:
0   Lync                          	0x009756ca 0x4000 + 9901770
1   libsystem_platform.dylib      	0x3b643058 0x3b63f000 + 16472
2   ???                           	0x0000039a 0 + 922
3   CoreGraphics                  	0x30826094 0x30819000 + 53396
4   libRIP.A.dylib                	0x30b72bc6 0x30b6a000 + 35782
5   libRIP.A.dylib                	0x30b7d1e8 0x30b6a000 + 78312
6   libRIP.A.dylib                	0x30b70934 0x30b6a000 + 26932
7   libRIP.A.dylib                	0x30b6f24a 0x30b6a000 + 21066
8   CoreGraphics                  	0x30823750 0x30819000 + 42832
9   CoreGraphics                  	0x308235e4 0x30819000 + 42468
10  UIKit                         	0x32fc4b54
Funny thing is although the app crashed, it wouldn't respring, so in my case [so far] I only get the apple logo, blackscreen quick reboot etc. only with that specific app (GoodNotes: great app, not sure they're to blame and must say they've been dilligent and helpful). I also own an iPhone 4S (2yrs +-) iOS 7.0.4, with the same app installed [but never really used it ~ seriously]. It has NOT resprung on a regular basis, nor can I say occasional [rare] reboots are related to any specific app; in fact I can't remember the last time it rebooted, so right now I'd say it's focused on the iPad. 
I have not yet tried any of the solutions listed above, except for turning off background updates (which I just did), even though GoodNotes isn't even on that list, and must say I am not really expecting this to solve the matter. [I'll let u know if I must take back these words and swallow them]
Bottom line: I expect Apple addresses this issue soon enough and shed a bit more light regarding the alleged graphics-memory link, because right now I refuse 2 undergo such a pain in the ass process as full, clean reinstalling EVERYTHING.
Cheers, have a nice day.