Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 1 user
Status: Duplicate
Closed: Jul 2013
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Sign in to add a comment
amd64 generic full - vmtests - security_ProfilePermissions.BWSI - Chrome sig 6 crash
Project Member Reported by, Jul 12 2013 Back to list
OS: Chrome

Seen on Chrome OS amd64 generic full builder here:

Notice the vmtest failure.  Snippet from log:

tmp.combined-control.E5rY7/security_ProfilePermissions.BWSI           [  FAILED  ]
tmp.combined-control.E5rY7/security_ProfilePermissions.BWSI             FAIL: Exception raised during login: Chrome automation failed prior to timing out, did chrome crash? for {"command": "GetLoginInfo"}. See the file named login-fail-screenshot.png in the results folder.
tmp.combined-control.E5rY7/security_ProfilePermissions.BWSI             07/12 15:22:08.578 ERROR|logging_ma:0579| [28275:28275:0712/] Failed to ConnectToRunningBrowser
tmp.combined-control.E5rY7/security_ProfilePermissions.BWSI             07/12 15:22:08.580 ERROR|logging_ma:0579| [28275:28275:0712/] Error during automation: Chrome automation failed prior to timing out, did chrome crash? for {"command": "GetLoginInfo"}

Stack dump found here:

full vm_test_results tarball attached.

What is the expected output? What do you see instead?
Test should pass, but fails when Chrome crashes.

Assigning to current Chrome gardener for triage.

9.4 MB Download
Comment 1 by, Jul 18 2013
Looks like this has been happening for a while on about 50% of runs. The oldest vmtest log I could fetch showing this error is build 8374 ( on Tue Jun 18 16:25:16 2013. We're getting an abort from this line:

Which means we got a failure in Bus::RequestOwnershipInternal (
Comment 2 by, Jul 18 2013
satorux, can you investigate / reassign appropriately?
Mergedinto: 234382
Status: Duplicate
Seems to be a dup of issue 234382

> We're getting an abort from this line:

LOG_IF(FATAL, !success) << "Failed to own: " << service_name;
Sign in to add a comment