Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Those are your words, not mine. What I portray here is some common sense. No tech company is perfect, as any internet forum will show. But that Apple supports a 6 year old system with their new OS is pretty impressive. It's a shame you are so intent on ignoring that.

No, not every system will work perfectly ever time. But if it works and is supported, there are a million reasons YOUR system may not work that have nothing to do with Apple. Accusing Apple of ignoring you is somewhat paranoid.

Apple has plenty of black marks, but there is no need to make up new ones. You need to relax and breath a little bit. Or not. Seems like the problem is yours, not Apple's.
It's not making up a new one. It's a class of machines that are claimed to be supported by apple, but are not - SOLELY due to problems with kexts. Apple is aware of the issue, has been for years, but does not fix the issue.

So Apple WILL and HAS refused to fix software issues, if it does not negatively impact revenue.

Claiming support, when these machines are in fact not supported should not be held up as a positive, like you are doing incessantly.

What thread are we in? The 1Gig of RAM debate. What are you constantly doing in here? Claiming it's a software issue that Apple will fix. What did I point out? A counter example.

I wish there was an ignore feature in these forums. Because I KNOW you will discount this, and continue claiming apple will guarantee fix this issue.
 
It's not making up a new one. It's a class of machines that are claimed to be supported by apple, but are not - SOLELY due to problems with kexts.

So a whole class of computer is not supported because of some posts in a forum? Is this another forum delusion of grandeur? :rolleyes:

Claiming support, when some machines are in fact not working should not be held up as a positive, like you are doing incessantly.

There, I fixed it for you.

I wish there was an ignore feature in these forums. Because I KNOW you will discount this, and continue claiming apple will guarantee fix this issue.

So when 7.1 or 7.2 comes out and fixes SAFARI, will that suffice for you? Or do you want an iPad recall to install 2GB of RAM for a problem that is not related to lack of RAM? of course I will discount this. It is nonsense.
 
You must have me confused with someone else. You do need a break. :rolleyes:

Of course there are issues. Last time I checked the people that design and build iPads are HUMANS. As such, there are bound to be issues. I don't "rail" against people having issues. I "rail" against people accusing Apple of insulting, ripping off, and all manner of illegal or inappropriate behavior.

Do me a favor and go back an reread my posts before you continue to confuse me with somebody else.

how many posts would you like me to find for you? dont make the number too high because i can't be bothered even though the evidence is there
 
lol i dont even need to search. how about three posts up

but i must have "confused you with someone else".. yea thats it. despite the fact that other people are saying the exact same thing about you. time to look in the mirror pal and tone down the blind fanboy support for apple
 
So a whole class of computer is not supported because of some posts in a forum? Is this another forum delusion of grandeur? :rolleyes:
Roll your eyes all you like. Known software kext issue that has not been fixed for many years. GPU related that does not effect all cards. Apple has refused to fix the software and has personally shot me down for service request of a busted situation.



There, I fixed it for you.
Super.



So when 7.1 or 7.2 comes out and fixes SAFARI, will that suffice for you? Or do you want an iPad recall to install 2GB of RAM for a problem that is not related to lack of RAM? of course I will discount this. It is nonsense.
The Air will not be recalled, that is non-sense. If they fix safari, I'd be happy. Seeing as probably the #1 app being used on the iPad's, I'd expect it to be addressed in some fashion. But given that they are selling a ton of them, what incentive do they have in fixing it. People are willing buying a product that has flaws, so no pressure.
 
The Air will not be recalled, that is non-sense. If they fix safari, I'd be happy. Seeing as probably the #1 app being used on the iPad's, I'd expect it to be addressed in some fashion. But given that they are selling a ton of them, what incentive do they have in fixing it. People are willing buying a product that has flaws, so no pressure.

I disagree, apart from business model and etc, there is a company ethics, morale also exist. So if something is buggy and not working properly, they will fix it. Im pretty sure apple will sort out all bugs :)
Speaking of bugs and safari, ive got my Air yesterday and spend quite a few hours on it recently and never had a single crash in safari, yet. Got it with 7.03 pre installed and updated it to 7.04 straight away. So far so good :)
 
I disagree, apart from business model and etc, there is a company ethics, morale also exist. So if something is buggy and not working properly, they will fix it. Im pretty sure apple will sort out all bugs :)
Speaking of bugs and safari, ive got my Air yesterday and spend quite a few hours on it recently and never had a single crash in safari, yet. Got it with 7.03 pre installed and updated it to 7.04 straight away. So far so good :)

Except for they fact that they haven't always done so.

As far as safari crashes, there are numerous links to be found here that will automatically cause a crash. Two other times that have a high chance of crashing safari would be a forum with embedded video. Between initial rendering of the page, and the subsequent rendering of the embedded video, there is a higher % of crashing. You can greatly increase the crash % by scrolling down the page in that situation. Scrolling quickly over a long page as soon as the page renders, also gives a higher % chance of crashing safari - embedded video or not.
 
Last edited:
We can all agree more RAM is better. None of us can definitely say the Safari is crashing on the new IOS devices because of the lack of ram. Safari occasionally crashes on my iPhone 5 and it has an A6 processor (32 bit).
 
We can all agree more RAM is better. None of us can definitely say the Safari is crashing on the new IOS devices because of the lack of ram. Safari occasionally crashes on my iPhone 5 and it has an A6 processor (32 bit).

iOS7 has something to do with it as well. My iPad2 crashed WAY more in safari, since the "upgrade" to iOS7.
 
None of the iOS devices are having true RAM issues under iOS 7. It's just a software bug that will be fixed eventually.
 
None of the iOS devices are having true RAM issues under iOS 7. It's just a software bug that will be fixed eventually.

link?

I don't see how you can definitely say that. Also, define issues. Many here would say that constantly refreshing tabs, and killing off other apps is a usability issue. I know I would.
 
link?

I don't see how you can definitely say that. Also, define issues. Many here would say that constantly refreshing tabs, and killing off other apps is a usability issue. I know I would.

Yes. That and safari crashes. I believe it's a software issue (causing crashes and reloads/using excessive RAM usage) and not a physical RAM shortage.
 
I agree this has to be a software issue. At least I really hope it is :( I've got a ton of low memory reports. My latest one about 10 minutes ago - with 1 tab in Safari and no other running apps.
 
Sorry to throw this in the mix but I've used some android tablets lately with more RAM and returned all of them. And I'm not very anal about lag to tell the truth but for some other reasons as well I didn't think I'd be happy with any of them for very long.

The Air I purchased has not given me personally any problems FWIW.
 
The Kit Kat upgrade for the Nexus 7 has made a significant improvement in lag. I expect the same for iOS 7.1 or 7.2. Fingers crossed.
 
Yes. That and safari crashes. I believe it's a software issue (causing crashes and reloads/using excessive RAM usage) and not a physical RAM shortage.

I agree, I think people may be confusing the LowMemory logs with crashing when they're likely unrelated. The app crashes seem to be fairly legit crashes (SIGABRT, bad address, etc). Perhaps an issue with the switch from 32-bit to 64-bit? Not sure, but when I've looked in the crash logs it really doesn't look like an out-of-memory condition that caused it. We'll see! Still doesn't happen to me frequently enough to even be an annoyance.
 
I agree, I think people may be confusing the LowMemory logs with crashing when they're likely unrelated. The app crashes seem to be fairly legit crashes (SIGABRT, bad address, etc). Perhaps an issue with the switch from 32-bit to 64-bit? Not sure, but when I've looked in the crash logs it really doesn't look like an out-of-memory condition that caused it. We'll see! Still doesn't happen to me frequently enough to even be an annoyance.

Yeah. My iPad mini (1) and iPhone 5C are behaving just like you guys are saying. Which is why I believe it's software. My mini1 is behaving like the new ones with only 512 MB RAM, that's suspect.
 
I agree this has to be a software issue. At least I really hope it is :( I've got a ton of low memory reports. My latest one about 10 minutes ago - with 1 tab in Safari and no other running apps.

my low memory reports list is longggggg, 2 weeks sine i bought it
 
I agree, I think people may be confusing the LowMemory logs with crashing when they're likely unrelated. The app crashes seem to be fairly legit crashes (SIGABRT, bad address, etc). Perhaps an issue with the switch from 32-bit to 64-bit? Not sure, but when I've looked in the crash logs it really doesn't look like an out-of-memory condition that caused it. ...

Running out of memory can cause all kinds of crashes. For example, if you request a new chunk of memory and forget to check that the call succeeded, then you reference the pointer and it is null or pointing at a random location, then you could get a segfault or null pointer reference or any number of errors, that don't specifically say "out of memory".

Assuming you've got memory is a very common mistake even in today's advanced programming languages. I can't tell you how much code I've seen where an object is created assuming it will just happen with no try/catch construct to make sure that it did. Heck, I've written lots of code like that when in a hurry. Fortunately, none of it was running on severely constrained platforms.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.