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

Issue 861626 link

Starred by 2 users
Status: Duplicate
Owner: ----
Closed: Jul 12
Cc:
█ sindhu.chelamcherla@chromium.org
kkaluri@chromium.org
dtapu...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Browser crashes on opening some website (Any URL of Github)

Reported by abhinic...@gmail.com, Jul 9 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3485.0 Safari/537.36

Steps to reproduce the problem:
1. Open https://github.com/ Website.
2. See the Crash error message.

What is the expected behavior?
1. https://github.com/ will open perfectly.

What went wrong?
1. Crash error message displayed.

Crashed report ID: c7119acb-d7d5-4481-a8e2-37cffc73a51e

How much crashed? Just one tab

Is it a problem with a plugin? N/A 

Did this work before? Yes Not Sure

Chrome version: 69.0.3485.0  Channel: canary
OS Version: 10.0
Flash Version: 30.0.0.134

This crash behaviour is happening on lots of other websites too.

Comment 1 by dtapu...@chromium.org, Jul 9

Labels: Needs-Feedback
Please provide the server crash id. Unfortunately the client crash id isn't of any use to us.

Comment 2 by rsleevi@chromium.org, Jul 9 

Do you have any other crash IDs? chrome://crashes should have some if they were properly uploaded to the crash server.

Comment 3 by abhinic...@gmail.com, Jul 9 

Uploaded Crash Report ID 96a64c0d3cd52328 (Local Crash ID: 20992705-8a04-4c17-8d43-2ce546703e90)
Crash report captured on Monday, July 9, 2018 at 11:52:18 PM, uploaded on Monday, July 9, 2018 at 11:52:20 PM

Is this will suffice?, I can see some more crashes which was also uploaded to the server.
Project Member

Comment 4 by sheriffbot@chromium.org, Jul 9

Cc: dtapu...@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

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

Comment 5 by rsleevi@chromium.org, Jul 9

Components: Blink>Layout
Thanks! Super-helpful. Adding Layout because its a crash in the layout engine.

Comment 6 by sindhu.chelamcherla@chromium.org, Jul 10

Cc: sindhu.chelamcherla@chromium.org
Labels: Needs-Feedback
Unable to reproduce this issue on reported version 69.0.3485.0 and latest canary 69.0.3487.0 using Windows 10. i.e; On browsing github.com/facebook.com/amazon.com not seeing any crash.

@Reporter: Please check the issue on fresh profile which do not have any apps/extensions added. Any further information on reproducing the issue would help in better triaging.

Thanks!
861626.mp4
3.9 MB View Download

Comment 7 by abhinic...@gmail.com, Jul 10 

After finding out the above comment, Disabled LayoutNG Flag in chrome://flags/ (Screenshot attached) solved the issue.

This issue is resolved and can be closed now.
chrome_canary_flags.PNG
6.6 KB View Download
Project Member

Comment 8 by sheriffbot@chromium.org, Jul 10

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

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

Comment 9 by rsleevi@chromium.org, Jul 10 

@Comment 6: Can you reproduce with LayoutNG? That sounds like a bug we'd still want to fix regardless :)

Comment 10 by abhinic...@gmail.com, Jul 10 

Yes, I enabled the same flag (Screenshot attached) and found the same issue happening.
There are some more flags enabled but only this one is giving issue on enabling.
Crash ID:
Uploaded Crash Report ID d5e8e2589fec3ccb (Local Crash ID: 16e0f3b3-b6f5-4891-96a0-c0e4f43d1dba)
Crash report captured on Wednesday, July 11, 2018 at 1:04:18 AM, uploaded on Wednesday, July 11, 2018 at 1:04:21 AM
chrome_canary_flags_enable_LayoutNG.PNG
6.8 KB View Download

Comment 11 by kkaluri@chromium.org, Jul 12

Cc: kkaluri@chromium.org
Mergedinto: 862797
Status: Duplicate (was: Unconfirmed)
The provided crash id is associated with Issue 862797, hence merging into it.
Please undo it, if it not the case...
►

Sign in to add a comment