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

Issue 834395 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 831953
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Chrome crash when try to upload for sent an image in facebook via chrome.

Reported by a.m.pla...@gmail.com, Apr 18 2018

Issue description

Device name: Asus ZenFone 5 (T00J)

From "Settings > About Chrome"
Application version:66.0.3359.106
Operating system:Android 5.0.0; ASUS_T00J Build/LRX21V

URLs (if applicable):https://m.facebook.com/

Steps to reproduce:
(1)login Facebook account 
(2)enter messaging option via chrome 
(3)select a friend and try to upload a picture, show a message "unfortunately, chrome has stopped ", and its comes twice.

Expected result:give option to upload picture from camera or storage 


Actual result:shown error 


 
Screenshot_2018-04-19-00-14-57.jpg
77.4 KB View Download
Labels: Needs-triage-Mobile
Cc: sandeepkumars@chromium.org
Components: UI
Labels: Triaged-Mobile Needs-Bisect
Status: Untriaged (was: Unconfirmed)
Tested the issue using #66.0.3359.106 on Asus Zenfone Max ZC5; 5.0.0 and could reproduce the Crash,

Working on bisect for this issue, will update the bug with bisect results soon.

Thanks!!
Cc: nyerramilli@chromium.org pnangunoori@chromium.org
Labels: -Pri-3 -Needs-Bisect hasbisect-per-revision FoundIn-66 RegressedIn-66 ReleaseBlock-Stable FoundIn-67 M-68 FoundIn-68 Pri-1 Type-Bug-Regression
Owner: agrieve@chromium.org
Status: Assigned (was: Untriaged)
Tested the issue in Android and able to reproduce the issue. 

Steps Followed:
1. Launch Chrome.
2. Navigate to https://m.facebook.com/ and logged in with valid credentials
3. Clicked on Camera on chat window
4. Observed the Crash

Chrome versions tested:
66.0.3359.106(Beta), 68.0.3400.0(Canary)

OS:
Android 5.0.0

Android Devices:
Asus Zenfone Max ZC5

Using the per-revision bisect providing the bisect results,
Good Build - 66.0. 3336.0  (533409)
Bad Build - 66.0. 3338.0  (534242)

You are looking for a change made after 533411(GOOD), but before 533412(BAD).

CHANGELOG URL:
The script might not always return single CL as suspect as some perf builds might get missing due to failure.
https://chromium.googlesource.com/chromium/src/+/7ee6c14b661b0abdfb91f8f0c8a07c34f1d353bc

From the CL above, assigning the issue to the owner concerned.

@agrieve:  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 owner concerned.

Please navigate to below link for log's--
go/chrome-androidlogs/834395

Note: 
1. This issue is not observed in Desktop.

Thanks!

Mergedinto: 831953
Status: Duplicate (was: Assigned)
Believe this to a dupe that is fixed on 67, but missed 66. All image uploads are broken :(

Sign in to add a comment