From Apple discussion:
OK, here is direct post from google translation (german to english).
-------------------------------------------------------------------------------- -----------------
Today I emailed the developer of the browser "iCab Mobile".
I would like to announce the findings of this developer and I thank you a thousand times for his truthful words.
Below is the mail traffic is very interesting ...
I = normal
Developer = fat
Reply-mail: 1
Various pages in third browsers like with my favorite browser "iCab
Mobile "
crash.
I could replicate the error with the site:
http://www.pocketpc.ch/magazin/testb...htc-one-m8-im-
detailed test-569 /
Yes, unfortunately this is a well-known problem of iOS 7
The general memory usage of the system itself is here apparently
increased significantly, but also the web engine has a massive problem
with the memory consumption. There are discussions in various forums, in
which the memory usage is discussed some JavaScript-structures,
and where it was then observed under 7.0.x that structures the iOS 6
only about 60 MB require iOS 7 times quite almost 10-fold to
Memory anforderten. This means that there are web pages even under iOS 5/6
still easily load on an iPad 2 with only 512MB RAM, iOS 7
on an iPad Air (with twice as much RAM), even in Safari (dar lack
Features and as part of the system too much memory saving
May be run in other browsers) lead to a crash. How far under 7.1
the whole has improved, I'm not sure yet. There are
but unfortunately still have problems.
Reply-mail: 2
1, So you can crash on ug page with iCab Mobile V8.1.1 and
IOS7.0.x replicate (all iOS devices)?
Yes, I can reproduce the crash, not only in iCab Mobile,
but also in Chrome and other browsers on an iPad Mini retina
with iOS 7.1.1. On iOS 6 on an iPad 3 (as much RAM as has
the mini: 1GB) running the same pages in the same version of iCab
Mobile without any problems. On iOS 6, the side needs many hundred MB of memory less.
2 May I make her answer in the forum public or to test the site
Calling iCab Mobile with, finally us with the knowledge cpl. new!
Clear. But as I said, any alternative browser should show the problem.
If necessary. well only when scrolling.
Many users turn instead to an Apple support to their iPad AIR
exchange, and am about ... (since many non affected).
Is certainly not a hardware problem. It is quite possible that a
Rebooting the device solves the problem for some time. And also various
System settings could the general memory usage of iOS
increase or decrease, and thus the problem more or less
can be likely.
3 If this site with your browser crashes it ought with a
IPAD AIR be other replicable or why I can not find the same
minded?
Although I have no iPad Air, but an iPad Mini retina, but
hardware technology in principle is identical. And I may be the problem
understand.
4 So crash logs do not help to optimize their browser?
Normally, yes. But in the case the reason is not so by iCab
causes, but from iOS itself means that here you can really only Apple
Remedy the situation.