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

Issue 748607 link

Starred by 4 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

UTILITY_PROCESS_CRASHED_WHILE_TRYING_TO_INSTALL

Reported by stevebro...@gmail.com, Jul 25 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.72 Safari/537.36

Steps to reproduce the problem:
1. Try to install Chrome Web Store App mjmjeiofkaojeccdogfjmbmpflopiofn
2. using Chrome 59 or 60 running on  Mac OS 10.11.6 or 10.12.4
3. 

What is the expected behavior?
App Installs sucessfully

What went wrong?
Error Message UTILITY_PROCESS_CRASHED_WHILE_TRYING_TO_INSTALL
App not installed (or not updated if already installed)
Suggested restart Chrome - this had no effect on the error
Also tried restarting cimputer - this had no effect on the error

Did this work before? Yes Up to about a week ago, not sure which Chrome build 

Does this work in other browsers? N/A

Chrome version: 60.0.3112.72  Channel: n/a
OS Version: OS X 10.12.4
Flash Version: 

The app installs successfully on Chrome 59 running on Mac OS 10.11.1 and on Windows 7. Not tested on any others.
This was first noticed on a regular update 0.26.93 of the app, so there was some change to the app that might have been responsible. However I then also uploaded a previous build 0.26.92 which had been successfully installed (with the version number only changed to 0.26.93.1 to allow the update) and this failed to install as well. So I do not believe it is anything to do with the app itself, reinforced by successful install onto Chrome on other operating systems.
 
Labels: Needs-Bisect Needs-Triage-M60
Cc: pnangunoori@chromium.org
Labels: Needs-Feedback
@stevebrooker123 -- Thanks for posting this issue. Could you please provide the respective URL of the application which you are trying to install. This would help us in further triaging the issue.

Thanks in advance.
Labels: -Needs-Feedback
pnangunoori@, here is the app link: https://chrome.google.com/webstore/detail/teammap/mjmjeiofkaojeccdogfjmbmpflopiofn?utm_source=chrome-ntp-icon

I am seeing similar error message on Win7 as well on Latest Canary#62.0.3168.0.
Cc: jmukthavaram@chromium.org
Labels: Needs-Feedback
Unable to reproduce the issue on Windows 7,Mac 10.12.6 & Ubuntu 14.04 using chrome reported version-60.0.3112.72, stable-60.0.3112.78 & Canary-62.0.3168.0 .

Able to add 'Team map' app successfully from webstore as per the URL mentioned in comment#3.

Please find the attached screencast for reference & let us know your observations on the same.
Thanks..!!
748607.mp4
1.7 MB View Download
Hmm.. interesting! Even i'm not seeing this issue anymore. Could something have been changed from app side recently?
I have not changed the app itself.
Just tried again and same error message
Screen Shot 2017-07-28 at 19.33.50.png
215 KB View Download
Just for the record OS 10.12.4  Chrome 60.0.3112.72 (Official Build) beta (64-bit).
Could it be that something has been left behind on my computer from a previous installation of the same app?
Project Member

Comment 9 by sheriffbot@chromium.org, Jul 28 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "jmukthavaram@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: TE-NeedsTriageFromMTV
As per comment#8,tested the same issue on Mac -10.12.5 (test machine) with chrome version-60.0.3112.72  & latest Canary-62.0.3172.0.

Able to install 'Team map' app successfully from webstore without any errors.
As Mac 10.12.4 is unavailable with chrome Hyd team, could some one from MTV team to please look into this issue.

Adding 'TE-NeedsTriageFromMTV' label for further investigation.

Thanks..!!
Cc: manoranj...@chromium.org
There is no point in testing Mac 10.12.4. I have now updated to 10.12.6 and the problem still exists with Chrome 60.0.3112.78 (Official Build) beta (64-bit).

I suspect this needs to be tackled from another point of view to attempting to replicating it, i.e. what is the error message telling us and from that what could be the causes? Could it be something left over from a previous installation. Are there any Chrome error logs on my machine that could be examined?
Cc: rdevlin....@chromium.org
Components: Platform>Apps
Are there any crash logs listed in chrome://crashes? We would need the crash ID.

rdevlin.cronin@ - any thoughts on figuring out the cause of this crash?
Cc: tbarzic@chromium.org
Hmm... possibility related to issue 713315 (restricted, but summary is that the utility process is killed for taking too long).

stevebrooker123@, about how long does the installation "try" before you see the error message?

Otherwise, we use the UTILITY_PROCESS_CRASHED_WHILE_TRYING_TO_INSTALL message when there's an error on the UtilityProcessMojoClient, which is normally called with connection issues (e.g., couldn't start a process).  I would expect a regular connection issue to be easily reproducible, though - Ken, are there any other reasons that UtilityProcessMojoClient::error_callback_ would be called?
About 18 seconds, NOT counting the download time.
the timeout in the code is set to 15 seconds, so this definitely does sound like it could be issue 713315.
This is still very much a live issue for my company and given the positive comments from rdevlin over a month ago I was hoping for some resolution of it by now.
Status: Fixed (was: Unconfirmed)
Should be fixed on M-61 by https://chromium.googlesource.com/chromium/src.git/+/e2129fc0c0290aa8191fa03970c59c3dcaf7a8af

(the same root cause as issue 713315)

Please reopen if that's not the case
Thanks very much. I can confirm the issue I was experiencing has disappeared.

Comment 20 by ajha@chromium.org, Oct 11 2017

Cc: mmanchala@chromium.org
 Issue 753826  has been merged into this issue.

Sign in to add a comment