Slashdot Mirror
Irony: iPhone 5S Users Reporting Blue Screen of Death
MojoKid writes "It's been a long time since many have seen a dreaded 'blue screen of death' (BSoD), but it's back and in the most unlikeliest of places. Oddly enough, some Apple iPhone 5S owners are reporting BSoD errors, though they're a little different from the ones you may remember seeing on Windows desktops. Rather than spit out an obscure error code with a generic description, some iPhone 5S devices are suddenly turning blue before automatically restarting. The Numbers app in Apple's iWork suite, a free program with new iPhones, seems to be the primary cause, though BSoD behavior has also been observed in other applications, according to complaints in Apple's support forum."
Guru Meditation: BSoD.
- In Soviet Korea, only old people loose all their bases to Natalie Portman's petrified hot grits overlords.
Aside from the whole 'a tightly sandboxed "app" taking down the system' thing (which makes one wonder if Apple's apps follow the same rules as everyone else's, or whether there is some Nasty bug in an API), don't iDevices use a totally different design for their screen of death? Macs, certainly, both PPC and Intel, can be made to execute BSOD-level crashes; but the process looks totally different.
Sounds like somebody's grammar checker had a blue screen...
Thanks to the War on Drugs, it's easier to buy meth than it is to buy cold medicine!
There is a great deal of evidence to indicate we are no longer capable of advancing software.
It has been remarked that if we built buildings the same way we build software the first woodpecker to come along would destroy civilization.
Take a look around. The government apparently spent $165 million on a web site that doesn't work.
There's no discipline in software development. It's slapped together to meet an artificial deadline. It's considered done if it compiles. It's shoved out into the marketplace so everyone can stuff their pockets and then all the developers are fired to make way for the new employees who will design the next piece of shit.
The only measure of how good software is depends on how shiny and "innovative" the user interface is. What the software actually does is utterly irrelevant.
... They're just looking at it wrong.
They didn't make a shiny golden backplate for you to waste your time looking at the screen, people!
. . .these turn out to be forced/silent restarts by Apple on the backend, due to a laundry list of reasons best left to others - don't ask how I know.
Uh oh, looks likes Job's Reality Distortion Field is collapsing. :p
If this keeps up, Macs may start turning into fruit or something.
It's Apple's new "iBoot" feature, which automatically restarts the phone when it detects an NSA probe, acting as if you noticed the spies and shut off your phone as a result. The more frequent your reboots, the more interested the goobernmint is in you. :P
I do not fail; I succeed at finding out what does not work.
also an apprenticeship system where you learn from pros in the field with real work. Not some professor reading from a book and / or loads of theory.
The crashes appear to only (mainly?) affect the new 64 bit CPUs. It would appear that some parts of the API/apps use code hardcoded to 32 bit applications. If this is really the case, then it should be a matter of time before bugfixes are released. It's not ok for a phone of that pricetag, but it isn't a complete disaster either.
I have seen people blame objective C as the culprit as some other programming languages have abstraction levels high enough to make the code immune to bugs due to CPU type. The thing is that C/C++/objC can write code with great performance, which translates to longer battery life. It is possible to write code immune to 32/64bit bugs in all of those 3 languages, but it takes more skill from the programmers and increase development time and costs. It doesn't surprise me if 64 bit considerations was skipped intentionally before Apple announced 64 bit phones. Testing 64 bit software before the 64 CPUs became available was naturally out of the question as well and 3rd party developers was given access to new phones possibly way too shortly before the release.
This excuse works much better for 3rd party software developers than for Apple as we would assume insight knowledge of new CPUs, but maybe it was secret inside as well due to risk of spies or leaks. It might also be a sign that the software was rushed a bit too much. People also complain about power usage in iOS 7, which also hints immature software.
I would dispute that. I don't recall MS-DOS ever crashing itself. True, programs were allowed such low level access to the PC hardware that they could cause a crash, but MS-DOS itself was rock solid and even program crashes were rare. I'm remembering all of the old demoscene stuff that used weird, undocumented functionality and were still stable.
Could it be in the iCloud API? Native apps like Numbers store docs in iCloud.
Apple is worse than Microsoft. People like to slam Windows 9x for being unstable, usually rightfully so, but they forget that the Macs of the time were even worse. By the time OS X came out, MS had Windows NT 4, 2K and XP out, which were all very stable. Since then, every MS OS has been stable, including Vista.
On top of that, Apple freaks out when people want to customize or doing something "out of bounds" with their Mac. Microsoft has always encouraged people to do what they want with Windows.
Apple is the new Microsoft.
Just with a shinier surface.
User apps are not allowed to use multitasking,
User apps are allowed to do anything for around ten minutes after they are shut by the user (they may be killed sooner if they use too many resources or the foreground app needs all the resources).
User apps can also have periodic tasks that run in the background (in iOS7).
User apps can also run indefinitely in the background under some conditions, like for navigation or... for background audio. So it might be some hiccup in the text to speech system operating while the app it is attached to is running in the foreground. I would think anything reading text generally would keep reading even if you closed the application, though it would depend on the application and how it set up the audio session...
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Here is video of an older iPhone and os making exact same blue screen/restart.
Seems to take different actions to trigger, but not sure this is a new bug.
From the comments sounds like it wasn't too uncommon either..
http://m.youtube.com/watch?v=KjyQLlEHomQ
-Lod
Your computer is broken. Have it repaired. (Or stop trolling... Sometimes it's hard to tell so apologies for giving a serious answer if so)
The typical Win 7 machine is impressively stable. I haven't seen a blue screen in years.
-Lod