
Tried to open up GoSkyWatch app and got this warning. The app opened fine many times before but this is the first time. Weak.
Well, it's probably more attributable to sloppy coding on the app developer's part (not being efficient, not checking when memory is getting full or taking steps to alleviate it, etc.)
Exactly, these errors happen all the time but you're never supposed to be alerted to them. I plugged my iPad into the SDK kit and found Safari had 3 of these errors from the first 4 days of use.
Yea the 256mb Ram is puzzling just given the higher resolution they should have upped it to 512mb. I think a v2 iPad will be out rather quickly probably in the fall along with OS 4.1 to address this and some of the other issues.
I wonder what will happen when multi-tasking is implemented. Will the iPad lock up? I admit that part of the problem could be due to inefficient coding but what will happen when many apps are running at the same time? Could this become a major issue? How about a free memory upgrade, yeah right! It should have been 512 from the start.
Yea the 256mb Ram is puzzling just given the higher resolution they should have upped it to 512mb. I think a v2 iPad will be out rather quickly probably in the fall along with OS 4.1 to address this and some of the other issues.
They won't make the same mistake twice by releasing a rev 2 too soon to upset rev 1 purchasers. It will be a year at the very least before you see the second version.
The memory issue in this case is from poor developing of this app software.
So, a developer releases a buggy app and it's apple's fault![]()
![]()
Tried to open up GoSkyWatch app and got this warning. The app opened fine many times before but this is the first time. Weak.
Yes, for releasing a cutting-edge device in 2010 and it comes with only 256mb of ram. All Apple had to do was to spend extra $5.5 to bump the memory to 512mb but chose not to.
As far as using iStats to free up memory, YOU SHOULD NOT HAVE TO DO THAT.
Yes, for releasing a cutting-edge device in 2010 and it comes with only 256mb of ram. All Apple had to do was to spend extra $5.5 to bump the memory to 512mb but chose not to.
Knowing this apparent crippling fact, the op still bought an iPad.
For too long now hardware has had to fix the problems created by people who shouldn't be programing.
Didnt Steve say, if you gotta look at a task manager you fail :lol: