Tested the issue using #65.0.3325.109 on Samsung J7; 7.0.0 as per the steps mentioned below.

Steps:
1. Launched Browser
2. Navigated to  https://codepen.io/anon/pen/geWEOv
3. Did not observe such behavior

@jonathan: Could you please help us with a sample screencast or screenshot with the exact issue which you're facing?

Thanks!!

Here you go!

Deleted: Screenshot_2018-03-24-14-11-44-846.jpeg 373 KB

	Screenshot_2018-03-24-14-11-44-846.jpeg 373 KB View Download

Thank you for providing more feedback. Adding the requester to the cc list.

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

I got the chance to investigate the issue a bit further, and it turned out that the limit was specific to my device, a Lenovo Tablet TB-X704L. 

I upped the size to 100MB in this codepen and it now prints out the error message to the DOM to make it easier to test: https://codepen.io/anon/pen/XEeZWe?editors=1011

Here are some additional devices that fail at 100MB or below: One Plus 3T, Samsung Galaxy S9+, Samsung Galaxy S8+, Samsung Galaxy A3. 

I want to note that this codepen works fine in Firefox on Android and Chrome/Safari on Iphone.

Able to reproduce the issue using #65.0.3325.109 on Samsung J7; 7.0.0 as per the steps mentioned below.

Steps:
1. Launched Browser
2. Navigated to https://codepen.io/anon/pen/XEeZWe?editors=1011
3. Observed "The reqeust file could not be read"

Working on bisect, will provide the info soon.

Thanks!!

dmurph@ - can you take a quick peek?

Since this is a synchronous load we may be running into Mojo pipe limits.

It's FileReader, not FileReaderSync. There shouldn't be any sync IPC here (at least not with any meaningful amount of data). 

I wonder if something is broken with disk backed blobs, and in particular with blobs that are immediately transported onto disk (i.e. 37MB is roughly the point when with 4GB RAM we immediately send a blob to disk (although not sure why the Samsung J7 would then need a larger blob to hit this, as that has less than 4GB ram afaict).

We got file reading error issues on Android in perf tests here:
https://bugs.chromium.org/p/chromium/issues/detail?id=823357

I wonder if that is related? We now have perf tests that exercise this transportation pathway.

It might be good to make some layout tests that do that too?

This seems to have been resolved, thank you!