Q: iPad Safari crashing regularly

So the question is then does that refresh button help? I still think the ultimate cause is a runaway process.

I would say the iPad 1 is more prone to crashing because of the 256MB RAM.

Another thing to watch is the CPU Usage especially the single core A4.

My iPad crashes several times during most sessions. I was looking at a Wash Post article (http://www.washingtonpost.com/world/national-security/former-cia-officer-charged -in-leaks/2012/01/23/gIQA3AhTLQ_story.html) tonight when it crashed four times. A couple of days ago it crashed when I was using the WSJ app, but that was the first time for that app; normally it is just Safari that crashes.

Apple just did their press event in NY -- about how sweet iTunes U is now. Except... you guessed it... every time I try to check out a class it CRASHES! How are students supposed to use text books on an iPad? Good luck with that!!

My iPad1 crashes seem to be on just about any webpage of any size.  Geez, Safari crashed when I logged in to write this reply.  I get plenty of low memory warnings for mail and Safari but I can't understand why an app should crash because of low memory.  I would think this would be handled with paging.

I've lived with this for seveeral months and it's awfully annoying.  I should would like some acknowledgement from Apple that this is being addressed.  I'm a real fan of the platform but this is burning me out and receiving no feedback from Apple is really discouraging.

Bill

It's sunspots! Solar maximum is frying our wifi and chips.

I have an ipad2 and it regularly crashes when I'm on message boards typing a response to something. It happens on a couple of different message board sites I visit

This is happening to me all the time anymore.  Eight times in the past 15 minutes.

Shut down all programs that are running in the background.

1. Double-click the Home button to see Apps in background

2. Hold the Apps down for a second or two until you see the minus sign

3. Tap the minus sign to close program

4. Reset iPad. Hold the Sleep and Home button down for about 10 second until you see the Apple logo

Suggest you perform Step 1 to 3 at the end of every day.

I stopped buying Windows products due to having to jump through hoops to keep my system running properly. Perhaps time to start looking at what others are offering. VERY disappointing Apple has not addressed this problem yet. Now I have experienced a couple crashes using Mail (in addition to the more routine browser crashes). My iPad 2 is wearing on my patience.

Apple may not have the answer. It's probably more of a symptom of bad App programming with App developers not paying careful enough attention to memory hogging functions and routines, especially when the App is not in use. In ways it reminds me sort of like how the Adobe flash plug-in was abused throughout the web by many (so called) developers. The more flash you got the slower your computer became, simply because developers did not know how to use the technology correctly. This bad behavior appears to be passing into the world of the Apps.

Stephen Bennett1 wrote:

 

Apple may not have the answer. It's probably more of a symptom of bad App programming with App developers not paying careful enough attention to memory hogging functions and routines, especially when the App is not in use. In ways it reminds me sort of like how the Adobe flash plug-in was abused throughout the web by many (so called) developers. The more flash you got the slower your computer became, simply because developers did not know how to use the technology correctly. This bad behavior appears to be passing into the world of the Apps.

It's not an App problem. With the exception of only a few Apps (media streaming Apps like Pandora) recently used Apps are NOT running and any memory they have used is available to be reused by the Operating System when memory is requested.

The crashes are likely due to incorrectly using a pointer to memory which has already been released resulting in an Illegal Address error. The problem is likely in Webkit which is used by Safari, other iPad Web browsers and some Apps.

We have to wait until Apple releases a fix for this.

That simple? This issue has been around long enough for Apple to fix.

You'd think they might have been able to divert a little bit of that $13,000,000,000 in profit from the last few months to getting Safari working properly....

Stephen Bennett1 wrote:

 

That simple? This issue has been around long enough for Apple to fix.

In complex multi-threaded software, bad pointer usage is one of the most difficult problems to find and fix. The problems are not reliably reproducible since they are affected by the order in which the end-user does things as well as being dependent on what he was doing previously (the state of the software).

The bad pointer could be the result of bad logic (release then reuse) or it could be do to a random store into the data area containing the pointer thus corrupting it. There are many other scenarios as well.

It's not "simple" at all.