one sec, no bother, im chilling at work.
----------
yeah those are crashing for me
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
clients iPad 3 Crashes on new site - please help me test
- Thread starter smartwill
- Start date
- Sort by reaction score
one sec, no bother, im chilling at work.
----------
yeah those are crashing for me
all of them have crashed for me so far... gd luck though
Thanks for testing. Appologies for not getting back to everyone but my imac crashed
I purchased an ipad 3 today and see that there is a problem. The site only crashes on certain pages. I personally think it's due the HIGH use of resources.
I would like to fix however don't know how. Any freelancers out there that would like to give it a try please reply to this thread!
Thanks for testing. Appologies for not getting back to everyone but my imac crashed
I purchased an ipad 3 today and see that there is a problem. The site only crashes on certain pages. I personally think it's due the HIGH use of resources.
I would like to fix however don't know how. Any freelancers out there that would like to give it a try please reply to this thread!
How large are those images (both pixel-wise and filesize-wise)? I think they might be far too high resolution for the web. Even on a powerful PC connected to DSL I'm finding the pages slow to download.
Think about people on a fixed amount of monthly bandwidth. That website will be murder on them.
Only the first one crashed for me on iPad 3 with Chrome (jailbroken, nitrous tweak installed) and after a fresh respring (roughly 820mb RAM).
The other three you listed were very slow, but worked.
The other three you listed were very slow, but worked.
I've now pretty much tried everything: I have reduced the number of image and resolution to extremely low however the site crashes when there are a few additional images added.
I found this: https://discussions.apple.com/thread/3896266?start=0&tstart=0
But how do you explain it to a client?
nick
worked on the Galaxy S3. Then again, did you expect anything else?
it just works
It also works on the Asus transformer prime
worked on the Galaxy S3. Then again, did you expect anything else?
it just works
It also works on the Asus transformer prime
This is most likely because those 2 devices are pushing significantly less pixels than the iPad 3, yet have the same memory. The retina is absolutely jaw-dropping, but it does eat up memory like a pig.
This is also probably the reason the iPad 2 is able to run it. Though it only has half the memory of those two devices, safari and iOS are so much more optimized and resource efficient than android that it can handle the website with half the memory yet an equal pixel density.
Last edited:
I have tested it on 6 different browsers
Chrome: ~5 seconds then crash
Safari: ~5 seconds
Perfect Browser: I was able to navigate to a few links (residental/leisure), but it inevitably crashed in maybe ~45 seconds
Icab: almost instant crash
Browser inside of the Goodplayer app: I was (surprisingly) able to get around for almost 2 minutes, but when it crashed, it crashed my whole device, not just the app.
Dual Browser: This one did not crash. However, it is a non-conventional browser, it is split down the middle so you can put a different website on each side, I don't think this is a viable solution for your case.
My conclusion is that it is, without a doubt, a memory related crash. Being jailbroken, I can see my available RAM at any moment, and after every crash it is under 100 (60-80mb), which in my experience, is the bare minimum apple with allow for the iPad 3 before force-closing apps. (It is usually just under 800mb without any apps running)
Last edited:
we expected you to read. No one asked about the s3. he wanted to know about the ipad 3
After a little more testing, I have discovered when the crashing occurs. Using the browser that doesn't crash, I can see severe fluctuations in the RAM as soon as you click any link. It drops from 600-700 to around 50-60, but after the page loads, it pops back up to 400-425mb and I can browse the loaded page with no problems. I suppose it is a matter of optimizing the initial loading of the page.
I'm not sure i understand.
When the button/ link is clicked the ram usage goes up to 600-700 mb and then drops to 50 - 60mb? Is that correct.. but then goes back up to 400 - 425mb when the transitions start again? But then it's o.k and you can brows the site?
Here is what happens:
-I have 600-700mb of RAM before I enter the website.
-As soon as I enter it, the number drops dramatically to 50-60 (this is when it crashes)
-A few seconds after that initial drop it goes back up to 400-425 and I can browse whatever page I am on, but if I click another link it will drop again to 50-60 for a few seconds before going back up.
On a normal browser, it will drop further than 50-60 and result in a crash. The initial RAM usage needs to be spread out in some way.
I was wrong about the transitions, they don't have as much to do with it as I thought.