New issue
Advanced search Search tips

Issue 772673 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Oct 15
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

chrome extension crashing only on chromeos beta and devel

Reported by dr.l...@gmail.com, Oct 7 2017

Issue description

Chrome Version: 61.0.3163.101
Chrome OS Version: 61.0.3163.101 (Official Build) beta (32-bit)
Chrome OS Platform: lenovo n23 yoga
Network info: happens on any network

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1) install Check Point chrome extension on chromeos from 
https://chrome.google.com/webstore/detail/check-point-sandblast-age/bnbpncoilnpdbcbfcegbjocobjppndlh
(2) once installed, left click the extension icon

Expected Result:
options dialog opens 

Actual Result:
the extension is automatically disabled/removed and i can see a repair button next to it

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
Always

What is the impact to the user, and is there a workaround? If so, what is
it?
cannot use the extension, not workaround

Please provide any additional information below. Attach a screen shot or
log if possible.
I created a movie that shows the problem:
https://app.hyfy.io/v/abJvPc8uguU/

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

It works properly on any other chrome (windows/mac) and also works when i manually load un unsigned crx in chromebook.
Seems like the signing process of this crx is adding an update_url entry in manifest.json and for some reason this causes a problem in chromebook.
 
Components: Platform>Extensions
looks like the referenced extension was updated 10/9.  Is this still reproducable?

Comment 2 by dr.l...@gmail.com, Oct 14 2017

I managed to find and fix the problem.
I was referencing a file in the wrong letter case (Divider.png instead of divider.png).
The only way to understand it was reproducing it in Ubuntu and looking at the debug logs (after running chrome in debug mode).
I think the misleading error message should be changed to help developers find similar problems in the future.   
Project Member

Comment 3 by sheriffbot@chromium.org, Oct 15

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

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

Sign in to add a comment