New issue
Advanced search Search tips

Issue 921102 link

Starred by 2 users
Status: Assigned
Owner:
chirantan@chromium.org
Cc:
vovoy@chromium.org
joelhockey@chromium.org
dgreid@chromium.org
sonnyrao@chromium.org
sienkou@google.com
tbuck...@chromium.org
rohi...@chromium.org
avkodipelli@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Crostini: Install large package from terminal and copy large files at same times crash chrome on x86_64 devices

Project Member Reported by sienkou@chromium.org, Jan 11 
Chrome Version: 71.0.3578.127
Chrome OS Version: 11151.113.0
Chrome OS Platform: nautillus, sona
Network info: wifi

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

Steps To Reproduce:
(1) After Linux VM creation completes, insert a USB drive. The drive has several directory / files, include a large Zip files (~4G)

(2) Open the Files app

(3) From Linux terminal, run sudo apt-get install libpango1.0. This installation will exit. Run sudo apt-get update per Debian's instruction to fix this issue

(4) After apt-get updates completes, re-run apt-get install libpango1.0. During the installation, from the Files app, copy paste files from USB drive into Linux files system and wait until both operation to complete

Expected Result:
 Both operations should complete without error

Actual Result:
 Screen eventually turns black, chrome browser would crash. Linux VM was shutdown unexpectedly

How frequently does this problem reproduce? (Always)

Note: This problem is only reproducible on x86_64 device. Same test did not trigger any error in arm64 (kevin)

Feedback link: https://listnr.corp.google.com/report/85901851616

Comment 1 by dverkamp@chromium.org, Jan 11 

The crash after copying large files may be https://crbug.com/905798 - however, it didn't require any interaction with the Linux VM (even copying a large file between two directories in Downloads should reproduce it).

Comment 2 by sienkou@chromium.org, Jan 11

Status: Untriaged (was: Unconfirmed)

Comment 3 by sienkou@chromium.org, Jan 12 

Note: Run same test on additional devices, repro on Nashier (x86_64) and not on dru (arm64)

Comment 4 by adlr@chromium.org, Jan 17 (6 days ago)

Cc: sonnyrao@chromium.org
Labels: -M-71 M-73
Owner: chirantan@chromium.org
This looks like a filesystem OOM situation.

Comment 5 by adlr@chromium.org, Jan 17 (6 days ago)

Status: Assigned (was: Untriaged)

Comment 6 by sonnyrao@chromium.org, Jan 18 (5 days ago)

Cc: vovoy@chromium.org
+vovoy


Seems like Chrome is crashing soon after we cross the threshold for tab discarding:

2019-01-11T18:14:34.443422+00:00 INFO kernel: [  523.293826] entering low_mem (avail RAM = 203680 kB, avail swap 2520268 kB, avail file 0 kB, anon mem: 634472 kB)
2019-01-11T18:14:34.449195+00:00 INFO localhos[6591]: crosvm[1]: [devices/src/virtio/balloon.rs:184] ballon config changed to consume 29744 pages
2019-01-11T18:17:36.654368+00:00 INFO crash_reporter[8670]: libminijail[8670]: mount '/dev/log' -> '/dev/log' type '' flags 0x1001
2019-01-11T18:17:36.792006+00:00 WARNING crash_reporter[8670]: [user] Received crash notification for chrome[1711] sig 11, user 1000 group 1000 (ignoring call by kernel - chrome crash; waiting for chrome to call us directly)
2019-01-11T18:17:36.792406+00:00 WARNING crash_reporter[8670]: [ARC] Received crash notification for chrome[1711] sig 11, user 1000 group 1000 (ignoring - crash origin is not ARC)

Do we have an id for that crash?
►

Sign in to add a comment