New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 751431 link

Starred by 2 users

Issue metadata

Status: Duplicate
Owner:
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression : Tab crash is seen after launching #62.0.3174.0 (32-bit) PGO build.

Reported by avsha...@etouch.net, Aug 2 2017

Issue description

Chrome version : 62.0.3174.0 (Official Build)  64 bit
OS : Windows (7,8,10)

What steps will reproduce the problem?
1. Install #62.0.3174.0 (32-bit) PGO build and launch it.
2. Observe. 

Actual Result : Tab crash is seen after launching #62.0.3174.0 (32-bit) PGO build.

Expected Result : Tab should not crash.

This is a regression issue broken in ‘M-62’, will soon update other info.
Good build : 62.0.3173.0
Bad build : 62.0.3174.0
 
Labels: Stability-Crash HasTestcase
Note : Unable to provide build revision and crash-id since nothing is accessible in 62.0.3174.0 (32-bit) Windows PGO build.
Actual_Crash.mp4
617 KB View Download
Cc: gov...@chromium.org abdulsyed@chromium.org ajha@chromium.org ligim...@chromium.org
Labels: -M-64 ReleaseBlock-Dev M-62
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on Windows 7, 10, will check and update bisect details once Win 64 PGO build is also available.
Note :  
1. Issue is also seen in Clang build #62.0.3174.2 (32-bit). Every page turns black in Clang build and un-installation process also takes several minutes.
2. This issue is specific to 32-bit (PGO & Clang) build versions only and same Clang #62.0.3174.2 (64-bit) build runs without any issues.

Kindly review an attached screen cast of Clang build.
Clang_Build.mp4
1.0 MB View Download
Cc: thakis@chromium.org
Components: UI>Browser
Owner: h...@chromium.org
Status: Assigned (was: Untriaged)
Able to reproduce the issue in PGO build #62.0.3174.0(32-Bit) and unable to reproduce in PGO-64bit and Clang-32 & 64 bit due to that unable to run the per revision bisect.So providing the manual bisect using below revisions.

Good build: 62.0.3173.0 (Revision: 490802)
Bad build: 62.0.3174.0 (Revision: 491203)

CHANGE-LOG URL:
---------------
https://chromium.googlesource.com/chromium/src/+/6a19f3216ade62e113277e4d5cb83b8705237d62

From the CL above, assigning the issue to the concern owner

@hans: Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.

Reviewed-On:https://chromium-review.googlesource.com/594636

Note: Windows specific issue not seen on Linux and Mac.

Thank you!


Comment 5 by h...@chromium.org, Aug 2 2017

Cc: sebmarchand@chromium.org
Owner: sebmarchand@chromium.org
My change only unbroke the pgo buildbots; there was no functionality change.

#3 says this reproduces in clang builds, but #4 says it's only pgo 32-bit?

It sounds like the repro steps is just to start the browser. Why isn't this breaking everywhere? Was 3174 a bad build?

+sebmarchand in case this is some kind of pgo issue.
Mergedinto: 749036
Status: Duplicate (was: Assigned)
This is the same compiler bug as in 749036.
Update :
This issue is also observed on latest #62.0.3175.0 & 62.0.3175.2 Windows Clang builds. Every page turns black immediatly after launching the build and nothing is accessible. This issue is specific to Windows OS and Linux & Mac (62.0.3175.0) builds are working fine.
Kindly review an attached screen-cast.

Thank you..
Clang_#62.0.3175.2_build.mp4
548 KB View Download
Note :
Issue is only seen on Windows(7,8) and it is working fine in Win-10 OS. Kindly review an attached chrome://gpu info for Windows(7,8) OS.
Win-7_GPU_info.png
626 KB View Download
Win-8_GPU_info.png
583 KB View Download
Can you bisect this?
Also, sounds like a different bug than the one here. Please file a new bug for that, and bisect there

Agreed that it's a different bug*, please open a separate issue for this.

* The previous bug was a MSVC compiler bug, this one is for build compiled with Clang and is maybe not a compiler bug as it's only affecting some specific versions of Windows.
The second bug above hin #c7 as been reported here https://bugs.chromium.org/p/chromium/issues/detail?id=752218, we can follow up there if there's no other dupes.

Sign in to add a comment