New issue
Advanced search Search tips

Issue 592203 link

Starred by 4 users
Status: WontFix
Owner: ----
Closed: May 2016
Cc:
ajha@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Chrome tabs remain blank

Reported by gabriele...@gmail.com, Mar 5 2016 
Chrome Version       : 50.0.2657.0 (Official Build) dev-m (64-bit) on Windows 10 64bit

What steps will reproduce the problem?
1. Opening any webpage, or any chrome special pages

What is the expected result?
1. The pages load correctly, or at least display some error

What happens instead?
1. The pages don't load at all and remain completely blank. Some tabs display a loading circle, which will keep spinning forever. Creating new tabs and closing existing ones work correctly and fluidly. New tabs remain blank, no speed dial is rendered. Chrome special pages are affected too.
2. After a while, a popup will show up, saying that some tabs are unresponsive. Pressing the Kill pages button on the selected tabs has no effect, and the popup remains open. Pressing the Wait button will close the popup, which will show up again after a short wile.

Please provide any additional information below. Attach a screenshot if
possible.
The browser was working fine till a few days ago, it started exhibiting this issue around the 3rd of March, 2016. Tried with a completely clean install using default settings. I have found two ways to restore the browser functionality, which could help identify the problem:
- Using the -no-sandbox option
- Using Windows 7 compatibility mode (Windows 8 doesn't work)

I can provide additional information if needed.
issue_1.png
25.6 KB View Download

Comment 1 by tong.kni...@gmail.com, Mar 8 2016 

Hi Im facing same issue on 49.0.2623.75 64bit m stable.

My company use Thin Client to connect to Windows7 virtual machine(XEN i think).

After a few attempts I found that same 32bit version chrome works fine in exact same platform, but 64bit version remains blank forever(exactly same as described).

Comment 2 by ajha@chromium.org, May 2 2016

Cc: ajha@chromium.org
Labels: Needs-Feedback
Anyone still seeing this issue on the latest stable(50.0.2661.94), please update here for further investigation.

Thank you!

Comment 3 by gabriele...@gmail.com, May 7 2016 

I don't know when it stopped happening, because I started using the workarounds I proposed in the first post, but I can confirm that on Chrome 52.0.2723.2 dev-m (64-bit) it doesn't happen anymore.
Thanks
Project Member

Comment 4 by sheriffbot@chromium.org, May 7 2016

Labels: -Needs-Feedback Needs-Review
Owner: ajha@chromium.org
Thank you for providing more feedback. Adding requester "ajha@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by ajha@chromium.org, May 9 2016

Labels: -Needs-Review
Owner: ----
Status: WontFix (was: Unconfirmed)
Thanks for the update. 

Closing the issue as per C#3. Feel free to file a new issue if such issues appear in future.
►

Sign in to add a comment