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

Issue 808813 link

Starred by 2 users

Issue metadata

Status: Unconfirmed
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

"Load Unpacked" likes to delete directories it was told to load

Project Member Reported by vapier@chromium.org, Feb 3 2018

Issue description

Chrome Version       : 65.0.3325.31 (it's been happening for a while)
OS Version: Linux

What steps will reproduce the problem?
1. git clone https://chromium.googlesource.com/apps/libapps/ 
2. cd libapps/nassh
3. ln -s manifest_v1.5.json manifest.json
4. ./bin/mkdeps.sh
5. open chrome://extensions/ and enable dev mode
6. select "Load Unpacked"
7. select the "libapps" dir
8. click "cancel" when it shows an error message
9. select "Load Unpacked"
10. select the "nassh" dir
11. see nothing happen
12. look at "nassh" dir locally and it's now been deleted!?

it seems to trigger more often when chrome is first loaded.

UserAgentString: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.31 Safari/537.36
 
Labels: Needs-Triage-M65
Cc: sc00335...@techmahindra.com
Labels: Needs-Feedback Triaged-ET
Unable to reproduce this issue on reported version 65.0.3325.31 using Ubuntu 14.04 with steps mentioned below. Attaching screencast for reference.

1. git clone https://chromium.googlesource.com/apps/libapps/ 
2. cd libapps/nassh
3. ln -s manifest_v1.5.json manifest.json
4. ./bin/mkdeps.sh
5. open chrome://extensions/ and enable dev mode
6. selected "Load Unpacked"
7. selected the "libapps" dir -- observed Could not load manifest file error -- selected I give up
8. selected "Load Unpacked"
9. selected the "nassh" dir and observed successful load of file but seeing error in chrome://extensions and observed nassh folder inside libapps 

@vapier: Please check the video and let us know if we miss anything. This would help in further triaging of the issue.

Thanks!
808813.ogv
8.7 MB View Download
this is still readily reproducible on my system (and i've seen it on multiple machines).  it isn't failing if i start with a clean profile (e.g. --user-data-dir=$HOME/foo).

i don't know how to look up what experiments my browser has been opted into, but it looks like i have at least chrome://flags/#enable-md-extensions turned on (not that i turned it on myself, but that i seem to have been opted in randomly).

i filed a feedback report referencing this bug by number, but i don't know if i can look at those logs either.

if i strace all of chrome, it def is nuking my dir:
13243 lstat("/usr", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
13243 lstat("/usr/local", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
13243 lstat("/usr/local/src", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
13243 lstat("/usr/local/src/libapps", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
13243 lstat("/usr/local/src/libapps/nassh", .......
...
13243 access("/usr/local/src/libapps/nassh/manifest.json", F_OK)            = 0
13243 open("/usr/local/src/libapps/nassh/manifest.json", O_RDONLY|O_CLOEXEC) = 155
...
13243 lstat("/usr/local/src/libapps/nassh/html", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
13243 getdents(335, /* 0 entries */, 32768) = 0
13243 madvise(0x94d3117e000, 1708032, MADV_DONTNEED)           = 0
13243 close(335)             = 0
13243 unlink("/usr/local/src/libapps/nassh/manifest.json")            = 0
13243 unlink("/usr/local/src/libapps/nassh/manifest_ext.json")            = 0
...a lot more unlink calls...
13243 rmdir("/usr/local/src/libapps/nassh/third_party/google-smart-card") = 0
13243 rmdir("/usr/local/src/libapps/nassh/_locales/cs") = 0
13243 rmdir("/usr/local/src/libapps/nassh/_locales/hr") = 0
13243 rmdir("/usr/local/src/libapps/nassh/_locales/vi") = 0
13243 rmdir("/usr/local/src/libapps/nassh/_locales/zh_CN") = 0
...a lot more rmdir calls...
13243 rmdir("/usr/local/src/libapps/nassh/third_party") = 0
13243 rmdir("/usr/local/src/libapps/nassh") = 0

where process 13243 is some thread of chrome's.  not sure how to look it up further externally.
# ls -l /proc/*/task/13243/exe
lrwxrwxrwx 1 vapier eng 0 Feb  7 16:22 exe -> /opt/google/chrome-unstable/chrome
Project Member

Comment 4 by sheriffbot@chromium.org, Feb 7 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "sc00335628@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: Needs-Feedback
Unable to reproduce this issue on chrome reported version 65.0.3325.31 using Ubuntu 17.10 with steps mentioned below:

1. git clone https://chromium.googlesource.com/apps/libapps/ 
2. cd libapps/nassh
3. ln -s manifest_v1.5.json manifest.json
4. ./bin/mkdeps.sh
5. open chrome://extensions/ and enable dev mode
6. selected "Load Unpacked"
7. selected the "libapps" dir -- observed Could not load manifest file error -- selected I give up
8. selected "Load Unpacked"
9. selected the "nassh" dir and observed successful load of file but seeing error in chrome://extensions and observed nassh folder inside libapps 

@Reporter:
Please find the attached screen cast for your reference and provide your inputs on it.

Thanks!
808813.mp4
8.2 MB View Download

Comment 6 by vapier@chromium.org, Feb 20 2018

Labels: -Needs-Feedback
i understand you might not be able to reproduce it.  but at this point, i've shown that it's def chrome processes wrongly deleting files, so someone who is familiar with these code paths should take a look.
As per comment#2 and #5 issue is not reproducible from TE end. Could someone from Platform>Extensions team please have a look into this issue.

Thanks!
Cc: -sc00335...@techmahindra.com sindhu.chelamcherla@chromium.org
Labels: TE-NeedsTriageHelp
As issue is not reproducible from TE end from comments#2,#5 and #7 adding TE-NeedsTriageHelp label. Could someone from Platform>Extensions team please help in triaging this issue.

Thanks! 

Sign in to add a comment