Why doesn't chrome swap memory to disk on android like it does on windows and Mac?!!My understanding is that it's too avoid wear on the sad/hand disk!!I really find this ironic as discarding and reloading tabs instead wastes CPU, GPU, and precious network bandwidth in exchange for slight reduction of wear on ssd. Not to mention the extreme disappointment to users for interrupted work flow (text input on forms lost, videos reloading from scratch).I really which google reconsiders this strategy as its would massively improve user experience on android.I'm currently using Firefox on android, which I believe swaps to disk and is much less annoying and battery friendly. On my nexus 9 I can have up to 10 tabs without reloading on Firefox while in chrome 2-3 tabs and everything keeps reloading.
Chrome on Android is slower after the update 42. The screen is more laggy if I'm scrolling. And the next main problem is, when the pictures are loading and I'm scrolling the screen, the screen turns grey, this problems are on War Thunder forum for example. Hope, that developers will fix it in next minor update. On Windows it is excellent now. Last thing, it takes a longer time when I open Chrome, I think it was better in version 42. I have Asus MemoPad ME102A-1B017A. Bye.
*Sorry, mistakes in this sentence. It takes a longer time, before the Chrome loads when I open him. And I think it was better in version 41.
And if I visit web page that I have visited before, the small picture (logo) of web page on the left corner didn't render correctly and it only render a white picture like on the new card when I start Chrome.
And the problem with grey screen is for example on Instagram too, and I think on all other pages where pictures are loading.
Post a Comment