New issue
Advanced search Search tips

Issue 872708 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 597700
Owner: ----
Closed: Aug 13
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

The browser did not respond when uploading the attachment and then crashed.

Reported by qiqihaob...@gmail.com, Aug 9

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36

Steps to reproduce the problem:
1. Open a webpage with the ability to upload attachments
2. Click to upload attachments
3. The browser did not respond when uploading the attachment and then crashed.

What is the expected behavior?

What went wrong?
The browser did not respond when uploading the attachment and then crashed.

Crashed report ID: 

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? Yes v67.0.3396.62

Chrome version: 68.0.3440.106  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
 
Cc: kkaluri@chromium.org
Labels: Needs-Feedback
qiqihaobenben@ Could you please help us 16 digit crash id from chrome://crashes for further triage.
Crash.png
15.1 KB View Download
I tried to reproduce this bug and then went to get the crash ID.After
trying many times, I found that there is no new crash data. There is only
one crash data today. I don't know if this problem is reported.

ID of the uploaded crash report: 8d701c397d28b959 (local crash ID:
d42503f2-840b-488b-8b3d-8720345fe497)




2018-08-10 20:19 GMT+08:00 kkal… via monorail <
monorail+v2.2099402154@chromium.org>:
Project Member

Comment 3 by sheriffbot@chromium.org, Aug 13

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
Cc: jbanavatu@chromium.org
Mergedinto: 597700
Status: Duplicate (was: Unconfirmed)
As per the crash id mentioned in comment#2 .The GPU driver in this issue seems a bit older.The driver supposed to contain the fix is >= 24.20.100.6025.

Stack trace of the crash id mentioned in comment#2 is same as Issue 597700. Hence merging into it.

Thanks!

Sign in to add a comment