Chrome browser process crashes when ejecting exFAT removable drive being accessed |
|||||||
Issue descriptionChrome Version: 57.0.2986.0 Chrome OS Version: 9194.0.0 Chrome OS Platform: Chromebook Pixel Also observed in 57.0.2970.0/9148.0.0 Chromebook Pixel 2. Steps To Reproduce: (1) Format an SD card in exFAT format (on Windows or whatever OS that supports it). (2) Put about 40 JPEG image files in the card. Each image should be large enough (>4000*3000px) so that it takes long time to load. (3) Create an HTML file in the SD card which loads all the pictures placed by (2) in a single document. Specify the box size of the images so as to make sure the images are visible to you in one screen while loading. For example, --------- <img src="0001.jpg" width=400 height=300> <img src="0002.jpg" width=400 height=300> <img src="0003.jpg" width=400 height=300> ... (36 more lines) ... <img src="0040.jpg" width=400 height=300> --------- (4) Open the HTML file in browser on the device. (5) Unplug the SD card physically, as soon as the first image starts to load (or a bit earlier than that). Expected Result: Images in the document fails to load, but the browser and the other apps continues to run. "Don't remove your device just yet!" notification message appears. Actual Result: The screen blacks out momentarily, then all the windows are closed. A new browser window starts telling "Chromium didn't shut down correctly." and prompts to recover the tabs. * How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) About 50%. This depends on the timing to eject the disk. It did not reproduce when I tried with ext2 and vfat. * What is the impact to the user, and is there a workaround? If so, what is it? When a user removes an SD card, it may crash all the apps. This affects not only the browser but other apps, like Files app and Gallery apps. One typical use case is with an SD card taken from a digital camera device, because /DCIM folder will be opened automatically by Files app when plugging such media. If the card is removed while Files app is loading image thumbnails inside the folder, it may trigger the crash. * Please provide any additional information below. Attach a screen shot or log if possible. [12602:12643:0120/215605.234808:FATAL:scoped_file.cc(40)] Check failed: 0 == ret. : Input/output error When close() returns an error (I/O error), the check here fails. https://cs.chromium.org/chromium/src/base/files/scoped_file.cc?q=%22PCHECK(0+%3D%3D+ret)%22&l=40 Also see Issue 677225 for specifics with Files app.
,
Jan 23 2017
,
Jan 23 2017
Can you reproduce this on a Linux desktop? I'm guessing that "Blink>Storage>FileSystem" isn't the right component. kinuko@, tzik@, what would be the right component?
,
Jan 23 2017
exFAT mounter on Chrome OS is implemented using FUSE, and that part is currently considered to contain the cause of this issue. It's probably possible to import that module to a Linux desktop system and test it, but will require a significant task. Some more findings: - It didn't crash when the SD card was locked (write-protected). - Also reproduced with 55.0.2883.103/8872.73.0 on Samsung Chromebook (released in 2012)
,
Jan 23 2017
OS>Kernel maybe?
,
Apr 21 2017
Issue 677225 has been merged into this issue.
,
Aug 22
,
Aug 22
,
Aug 23
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by yamaguchi@chromium.org
, Jan 20 2017