Blank tab appears if i open more than 2 in Google Chrome, very very annoying

[raddy]

Hello Everybody

I am unable to use Google Chrome browser in my mobile phone.
I heard that the blank page issue in Google Chrome only dogged the nVidia Tegra based devices.
But even i am facing the very same issue and the work around mentioned where not useful.
I had to kill the application and re-open it to use it.
I can't use more than one tab in Google Chrome.

I have upgraded my mobile phone to a powerful HTC One X from Google Nexus S to use Google Chrome too.
As Google Chrome functioned very slowly in Google Nexus S.
But now Google Chrome in my HTC One X is unusable.

Can anybody suggestion solutions ?

 

[raddy]

I will explain my problem in depth now.

1 --> Open Google Chrome
2 --> Visit www.slashdot.org or any website
3 --> Open new tab and visit altavista.com or any website
4 --> Click the tab number button and switch to first tab.

Expected behavior

First tab should be loaded now.

But instead of that, first tab would reload into a blank tab.
Then i can switch to second tab either.
Even if i close all the tab, i won't be able to visit any sites in new tab there after.
So, i have quit Google Chrome by pressing the running application button.

Running 2.20 version of stock software.

 

[phishie]

This issue has been reported to Google and is known, star these issues so Google will work on them.

http://code.google.com/p/chromium/issues/detail?id=130607

http://code.google.com/p/chromium/issues/detail?id=113204

Also, if you look at the reviews of the Google Chrome reviews on the Play store written by HTC One X users you will see many people are having the issue.

I'm having the issue on a stock One XL 2.20, I've simply gone back to using the stock HTC browser for now.

 

[WookieFan]

As above, I have noticed this behavior as well with Evita on stock ROM.

Here are some more details :

The blank tab appears to indicate a crash in Chrome. Once the blank tab appears, you cannot close tabs or close Chrome without the application manager.

How I avoid the issue:

Always close all tabs before leaving Chrome to use other apps.

Use ES Task manager to clear all cache before starting new Chrome session. I do not suggest using task manager for any other purpose.

The issue appears to be a memory issue. If I forget to clear cache and Chrome crashes, the only way to get Chrome operational again is to restart my Evita.

Hope this helps.

Sent from my HTC One X using Tapatalk 2

 

[911jason]

Same problem here, just popped up today for the first time though.

 

[phishie]

I've had this issue with Google Chrome on my stock AT&T One XL for at least 2 or 3 months. I got sick of it very quickly and switched back to the HTC browser. I still use Chrome at least once a day or so but it crashes too often to be my main browser now.

 

[adulel08]

you would think chrome browser would be the BEST for our Google phone by now, like it but thats the reason why i stack on stock browser too

 

[Zoide_]

I experienced the Chrome issue on my AT&T HTC One X with the 2.20 ROM since day 1. I rooted the phone and unlocked it, then installed CyanogenMod 10, and the problem seems to be fixed.

 

[WookieFan]

I experienced the Chrome issue on my AT&T HTC One X with the 2.20 ROM since day 1. I rooted the phone and unlocked it, then installed CyanogenMod 10, and the problem seems to be fixed.

Running CleanROM now, so we'll see if the issue persists...

Sent from my HTC One X using Tapatalk 2

 

[style2burn]

Running CleanROM now, so we'll see if the issue persists...

Sent from my HTC One X using Tapatalk 2

WAs the issue fixed on cleanROM? i recently rooted and went to cleanROM and the chrome issues have been bothering me from day one but havent' tried it yet since I rooted.

 

[raddy]

Hello Everybody

Thanks to everybody for sharing their thoughts.
I am not interested in rooting / modding my mobile phone as of now.
Even though i am not new to this, i just find it too cumbersome and provides less incentive.

I thought the issue in question happens only because of nVidia Tegra Drivers.
Experiencing the same issue even in Qualcomm Snapdragon S4 based mobile phone, frustrates me.
I am not sure whom to blame for this.

It would have been great if HTC put a work around for the Google Chrome's incompatibility issue in it's flagship mobile phone.
I hope Samsung Galaxy S3 users would happily be using Google Chrome in their large screen mobile phone.
The issue is still piggy back in elavate Jelly bean build is unacceptable.

 

[WookieFan]

WAs the issue fixed on cleanROM? i recently rooted and went to cleanROM and the chrome issues have been bothering me from day one but havent' tried it yet since I rooted.

I have only been running CR 4.5 for about 36 hours, but it looks good so far. I had five tabs open last night, left browsing for a while and all tabs refreshed properly. I'll check in again in a few days.

Sent from my Nexus 7 using Tapatalk 2

 

[style2burn]

I have only been running CR 4.5 for about 36 hours, but it looks good so far. I had five tabs open last night, left browsing for a while and all tabs refreshed properly. I'll check in again in a few days.

Sent from my Nexus 7 using Tapatalk 2

The browser works great on cleanROM EXCEPT for chrome has horrible horrible battery drain. Even with "scroll tilting" off, it still uses 10+%. I suspect because its constantly refreshing and syncing with the desktop..which is a shame because its what I WANT it to do.

Also, makes my HTC one x very warm, i haven't had that issue since I first got it, and disabled GPS

 

[raddy]

This issue has been reported to Google and is known, star these issues so Google will work on them.

http://code.google.com/p/chromium/issues/detail?id=130607

http://code.google.com/p/chromium/issues/detail?id=113204

Also, if you look at the reviews of the Google Chrome reviews on the Play store written by HTC One X users you will see many people are having the issue.

I'm having the issue on a stock One XL 2.20, I've simply gone back to using the stock HTC browser for now.

If this bug is caused because of Tegra driver issue, then why this issue occurs in our Snapdragon based HTC One X?