IOS 8.0.2 = crashing webpages

Have you tried a reset (hold the power and home keys down until the Apple logo appears)?

Barry

P.S. I agree that beta testing should not be part of the task of people installing a general release.

MatsSvensson wrote:

Nope, that did no difference.

What is that supposed to do?

The pad looked like it was rebooting, but after that the same programs seemed to still be open.

Does IOS not actually reboot properly when you restart it?

A reset (akin to resetting the SMC on a Mac) sometimes fixes odd problems. Did you hold the keys down until the Apple logo appeared? Otherwise you just restarted it. As I recall, when I reset my iPad (it has been a while), nothing was open from before.

Barry

I have noticed other reports of wi-fi connectivity problems from users who have installed iOS 8.0.2. Although I usually install everything when it is first released (pioneers have arrows sticking out of their backs 😝) I have deferred iOS 8.0.2 so I have no first hand experience. I have also seen others who have had no problems.

All of that is of no help to you 😟. Since downgrading is not supported, I am sorry to say I have no other ideas.

Barry

You are not doing it right.

Hold the top button until you see "slide to power off". Slide it to the right and it will power off. it takes a minute to power off, so wait a couple of minutes. Then hold the top button again top power it on.

The previous post is NOT correct. A reset is accomplished by holding the power and home keys down at the same time until the Apple logo appears. This takes 10-15 seconds, not a minute.

Barry

+1. This seems to be a Safari issue. Was there for 8.0 and 8.0.1 release, hopefully they address it in the 8.0.3 release when that comes? It's very annoying.

+1, what actually happens is that WebKit (Safari) crashes while parsing/executing javascript, below is an excerpt from the call stack:

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x00000002
Triggered by Thread: 0

Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 ??? 0x03b259d0 0 + 62020048
1 ??? 0x03b1bdfc 0 + 61980156
2 ??? 0x03b0f540 0 + 61928768
3 ??? 0x03b1961e 0 + 61969950
4 ??? 0x03b23d44 0 + 62012740
5 ??? 0x03b24d5a 0 + 62016858
6 JavaScriptCore 0x24fa0e86 llint_entry + 20198
7 JavaScriptCore 0x24fa0ed4 llint_entry + 20276
8 JavaScriptCore 0x24fa0ed4 llint_entry + 20276
9 JavaScriptCore 0x24fa0fda llint_entry + 20538
10 ??? 0x03a85e78 0 + 61365880
11 ??? 0x03aa28fa 0 + 61483258
12 ??? 0x03a772c6 0 + 61305542
13 ??? 0x04997816 0 + 77166614
14 JavaScriptCore 0x24fa0e86 llint_entry + 20198
15 ??? 0x04997816 0 + 77166614
16 JavaScriptCore 0x24fa0ed4 llint_entry + 20276
17 JavaScriptCore 0x24fa0ed4 llint_entry + 20276
18 JavaScriptCore 0x24f9bd8c callToJavaScript + 332
19 JavaScriptCore 0x24f2c660 JSC::JITCode::execute(JSC::VM*, JSC::ProtoCallFrame*) + 32
20 JavaScriptCore 0x24d7c4ba JSC::Interpreter::executeCall(JSC::ExecState*, JSC::JSObject*, JSC::CallType, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&) + 346
21 JavaScriptCore 0x24e6fb1c JSC::call(JSC::ExecState*, JSC::JSValue, JSC::CallType, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&, JSC::JSValue*) + 60
22 WebCore 0x2f0b59ae WebCore::JSEventListener::handleEvent(WebCore::ScriptExecutionContext*, WebCore::Event*) + 558

Some feel it won't be until after the Apple event later this month before bringing out a new update and some think it will be even later. One this for sure, there is no sure time frame for when the unresolved issues with IOS 8 will be fixed. It's a waiting game.