New issue
Advanced search Search tips

Issue 731670 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Chrome "Insufficient Memory" issue

Reported by m.xan...@gmail.com, Jun 9 2017

Issue description

Steps to reproduce the problem:
1. Open Chrome
2. Go to gmail web
3. Create new email
4. Add an attachement

What is the expected behavior?
The attachment is correctly upload.

What went wrong?
Chrome responds with an error saying "Insufficient Memory".

Did this work before? N/A 

Chrome version: 58.0.3029.83  Channel: n/a
OS Version: 5.1.1
Flash Version:
 

Comment 1 by m.xan...@gmail.com, Jun 9 2017

We are working on a webapp and are facing a weird "Insufficient Memory" issue when trying to upload a file using Chrome on Android mobiles.
It happens for some combinations of Mobile Model + Android Version + Chrome. Sure it does on Galaxy Note 3 Lite (SM-N7505) with Android 5.1.1 and Chrome 58.0.3029.83.

We tried to upload pictures to facebook and gmail but the issue comes up. We made some attempts by clearing Chrome cache, by using Desktop Mode and by using the Anonymous Mode without any luck.

The only way we found to avoid the issue is to uncheck the "Don't keep activities" developer option on the device and, unfortunately, this is not a reasonable workaroud for final users.

Let me said that Firefox doesn't suffer this issue but almost all of our final users use Chrome.

Is there a way to avoid this issue on Chrome?
Cc: tedc...@chromium.org
We were unable to repro this, attachment was successful, when tested on Samsung Galaxy Note 3 (SM-N750)/5.1.1, Chrome: 58.0.3029.83. 


Cc: finnur@chromium.org
Don't keep activities isn't something any user should select.  By doing that, Chrome is killed when we show the file picker and there is no way around that.

There is some work to see if we should handle file selection ourselves, but having don't keep activities set and expecting this to work is a bad combination.

Comment 5 by m.xan...@gmail.com, Jun 10 2017

Ok. Got it. I was wrong believing the "don't keep activity" option was checked by default. Turning off developer options let Chrome works correctly.

This is not an issue.

Comment 6 by finnur@chromium.org, Jun 12 2017

Not sure how to read the above. Was the problem with "Developer Options" or "Don't keep activities" and the bug can be marked as Fixed or do we still have an underlying problem that needs to be addressed?

Comment 7 by m.xan...@gmail.com, Jun 12 2017

I was facing this issue because the "Don't keep activities" was on on my mobile. I turned off "Developer Options" (which include the "Don't keep activities" option) since our final users will never use them and consequently will never face the issue.

The issue can be marked as fixed since "Chrome is killed when we show the file picker and there is no way around that" which is Chrome normal behaviour.

Comment 8 by finnur@chromium.org, Jun 12 2017

Status: WontFix (was: Unconfirmed)
Good to know. Thanks for the update! Closing.

Sign in to add a comment