Ipad air low memory crash

One problem with that. I don't wait 15 seconds for a page to load, and I aint about to start now.

Apple has fixed the issue regarding Crash Logs in iOS 7.1

- - -

http://www.pc-tablet.com/31462-apple-ipad-users-expecting-ios-7-0-4-update/

Crash Logs

Known Issue

Crash logs will not appear in Diagnostics & Usage Data in Settings. The logs will still be available when synced off the device.

- - -

No more crash logs to upset us ...

Sorry :-( but what does it mean this statement?!?

- "Crash logs will not appear in Diagnostics & Usage Data in Settings. The logs will still be available when synced off the device."

Have they solved the problem or they are going just to hide it in Diagnostic logs?????

I am a little confused :-((((((

Can someone better explain this point?

Thank you very much

Regards

Fabio

I quote a comment from this site (9to5Mac: Apple iPhone, Mac and iPad News Breaking All Day)

"Crash logs will not appear in Diagnostics & Usage Data in Settings.”

How better to make sure users don’t see all those Low Memory Warnings spurting from their nice shiny new iPads? Shameful. This is an absurd change with no rationale other than to hide the real reason for most iOS crashes from the non-power user (lack of RAM). Just should have put in 2GB of RAM.

Of course, that sire crashes.

Most of us would never have known about the logs if not for the crashes.

Apple could afford to put 4gb of ram. These aren't effffing Kindles, which by the way have more ram!

Thanks Yellowtail714 for your reply and your suggestion to fast scroll on the 9to5.com link.

Yep...my Air crashed Safari consistantly, in addition some web pages had a double image and eventually Safari freezed!

Back to the Apple store; showed them Safari crash video and screen shots of the double image problem...Tech agreed there was an issue and replaced my iPad with a new one...

Tried the same test on x2 Apple store iPad Airs... none failed.

Could people please tell when they purchased their Air's. I just received mine and tracked it from China, so it is one of the newest ones. I have not used it yet (Christmas gift) but just wondering if they might have had most of the issues with the first batches.

For what is worth…

Placed the order on November 29^th

Received the unit from China December 6^th

Test 1

I can scroll up and down on the link below as fast as possible, no crush doing that, but the moment I enlarge text Safari crushes.

Link: http://9to5mac.com/2013/11/08/a-week-with-the-ipad-air-in-three-words-believe-th e-hype/.

Test 2

I can scroll up and down on the link below as fast as possible, no crush doing that, but after closing this link Safari would not open, it tries to lunch but closes immediately, I have to clear Browsing Data and Cash and then Safar would open again

Link: http://www.visions4.net/journal/time-line/page-two/page-two-a/page-three/page-th ree-a/page-five/

Test 3

No problem in iTunes when playing move trailers in horizontal orientation or switching the orientation.

Not good that those who are having insights on 7.1 (in beta now) are not mentioning any memory problems fix, aside that 7.1 is happening sometime in first quarter of 2014.

Thanks,

Misha

I ordered it on the first day it was released, and it was also shipped from China. I doubt if there have been any hardware changes since the Air was released.

Safari on Ipad Air crashes all the time. At least a few times a day. I keep hoping a new update will fix the problem but it still happens with 7.0.4. It's starting to make me hate my new Ipad. I had an Ipad 3 before this and it never happened. Why do we always hear about other minor bugs in the media and never this? It seems like there are a lot of people having this same problem, and if the media would report it, maybe Apple would do something about it? Look how long this thread is -- don't tell me Apple doesn't know there's a problem.

Apple censors any bad press. Btw my iPad 3 crashed all the time since I installed iOS 7.0.0 it was terrible. Made me go out and buy an air. Maybe I should have got a surface but the weight on the surface and shape did not appeal to me as nicely as the design of the iPad. Hopefully they figure this crap out. Maybe we are all lucky and have bad ram???

I found this Crash Log on my Air reporting a CPU overload when using Safari. Here is the first part of the log plus the thread that caused the crash. Has anyone seen this log on their Air?

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>AutoSubmitted</key>

<true/>

<key>SysInfoCrashReporterKey</key>

<string>e9827d5984f51d860f25fed4f5c6bdeee84b1987</string>

<key>bug_type</key>

<string>185</string>

<key>bundleID</key>

<string>com.apple.mobilesafari</string>

<key>description</key>

<string>Incident Identifier: 495C4FB0-CC57-4B2D-99C8-7818AD318CC2

CrashReporter Key: e9827d5984f51d860f25fed4f5c6bdeee84b1987

Hardware Model: iPad4,2

Process: MobileSafari [784]

Path: /var/mobile/Applications/8681421D-8025-4B05-BCD5-B5AAFA3BD2AA/MobileSafari.app/ MobileSafari

Identifier: com.apple.mobilesafari

Version: 9537.53 (7.0)

Code Type: ARM-64 (Native)

Parent Process: launchd [1]

Date/Time: 2013-12-11 18:46:50.068 +1100

OS Version: iOS 7.0.4 (11B554a)

Report Version: 104

Exception Type: EXC_RESOURCE

Exception Subtype: CPU

Exception Message: (Limit 50%) Observed 84% over 180 secs

Triggered by Thread: 2

Thread 0:

0 libsystem_kernel.dylib 0x0000000199305cc0 0x199304000 + 7360

1 CoreFoundation 0x000000018c7a2ca8 0x18c6d8000 + 830632

2 CoreFoundation 0x000000018c7a0e9c 0x18c6d8000 + 822940

3 CoreFoundation 0x000000018c6e1b34 0x18c6d8000 + 39732

4 GraphicsServices 0x00000001920c382c 0x1920b8000 + 47148

5 UIKit 0x000000018f7200e4 0x18f6a4000 + 508132

6 MobileSafari 0x00000001000652ec 0x10005c000 + 37612

7 libdyld.dylib 0x0000000199223a9c 0x199220000 + 15004

Thread 1:

0 libsystem_kernel.dylib 0x0000000199305ac8 0x199304000 + 6856

1 libdispatch.dylib 0x0000000199209d74 0x199204000 + 23924

Thread 2 name: WebThread

Thread 2 Crashed:

0 JavaScriptCore 0x000000018d9a4c0c 0x18d9a0000 + 19468

1 WebCore 0x0000000196010c78 0x195d5c000 + 2837624

2 WebCore 0x0000000196010988 0x195d5c000 + 2836872

3 WebCore 0x0000000196097328 0x195d5c000 + 3388200

4 WebCore 0x000000019609745c 0x195d5c000 + 3388508

5 WebCore 0x00000001960105ac 0x195d5c000 + 2835884

6 WebCore 0x000000019601020c 0x195d5c000 + 2834956

7 WebCore 0x000000019601020c 0x195d5c000 + 2834956

8 WebCore 0x000000019601020c 0x195d5c000 + 2834956

9 WebCore 0x000000019601020c 0x195d5c000 + 2834956

10 WebCore 0x0000000195e7c748 0x195d5c000 + 1181512

11 WebCore 0x0000000195e77304 0x195d5c000 + 1159940

12 WebCore 0x0000000195f3f6d0 0x195d5c000 + 1980112

13 WebCore 0x0000000195f3f618 0x195d5c000 + 1979928

14 WebCore 0x0000000195f44a94 0x195d5c000 + 2001556

15 WebCore 0x0000000195f44a68 0x195d5c000 + 2001512

16 ??? 0x000000016790ed90 0 + 6032518544

17 WebCore 0x0000000195da1580 0x195d5c000 + 284032

18 WebCore 0x0000000195da0f40 0x195d5c000 + 282432

19 WebCore 0x0000000195da0288 0x195d5c000 + 279176

20 WebCore 0x0000000195d9fd90 0x195d5c000 + 277904

21 WebCore 0x0000000195d9fcd0 0x195d5c000 + 277712

22 CoreFoundation 0x000000018c7a3688 0x18c6d8000 + 833160

23 CoreFoundation 0x000000018c7a32f8 0x18c6d8000 + 832248

24 CoreFoundation 0x000000018c7a1020 0x18c6d8000 + 823328

25 CoreFoundation 0x000000018c6e1b34 0x18c6d8000 + 39732

26 WebCore 0x0000000195e5cb98 0x195d5c000 + 1051544

27 libsystem_pthread.dylib 0x00000001993a01ac 0x19939c000 + 16812

28 libsystem_pthread.dylib 0x00000001993a0104 0x19939c000 + 16644

29 libsystem_pthread.dylib 0x000000019939d7ac 0x19939c000 + 6060