New issue
Advanced search Search tips

Issue 607482 link

Starred by 7 users

Issue metadata

Status: Duplicate
Merged: issue 574442
Owner: ----
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Chrome stores memory that will never be released when taking picture from Camera

Reported by esteban....@gmail.com, Apr 28 2016

Issue description

Steps to reproduce the problem:
1. Create any scenario as simple as with a "<input type="file" accept="image//*" capture="camera" multiple> " field
2. Upload an image from Documents, check in Settings that Chrome's "Data" memory won't increase. 
3. Upload a video from the Camcorder, check in Settings that Chrome's "Data" memory won't increase.
4. Upload a picture taking it directly form the Camera. Chrome's "Data" memory will increase without saving it anywhere. 

What is the expected behavior?
Data memory should not increase if we upload a picture unless we explicitly save it to the local storage. Or at least it should eventually release it.

What went wrong?
Memory should behave equally when uploading a file from Documents, Camcorder or Camera.

Did this work before? Yes Chrome Mobile version 42.0.2311.111

Chrome version: 50.0.2661.89  Channel: stable
OS Version: 5.0.2
Flash Version: Shockwave Flash 21.0 r0

Also failed in version 49.0.2623.105
 
Owner: qin...@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 2 by wadel...@gmail.com, May 26 2016

This bug concerns me as well. Thank you for looking into it!

Comment 3 by wadel...@gmail.com, May 26 2016

It would be nice to hear if anything can be said concerning the progress of this issue. Of course, if someone would need additional information/testing/... I would be glad to provide.

Comment 4 by wadel...@gmail.com, Jun 16 2016

A small project to automatically reproduce this issue can be found here: https://github.com/wdlb/chrome-pictures-storage-issue

Comment 5 by wadel...@gmail.com, Apr 27 2017

Any updates on this bug? This is still being an issue for our clients. Or does anybody knows about a possible workaround, eg cleaning the Data memory from Javascript?

Comment 6 by tkent@chromium.org, May 8 2017

Cc: mlamouri@chromium.org rbyers@chromium.org
 Issue 716368  has been merged into this issue.
Cc: mcasas@chromium.org qin...@chromium.org
Components: Blink>ImageCapture
Owner: ----
Status: Untriaged (was: Assigned)
mcasas@, are you the right person to look at this?

Comment 8 by mcasas@chromium.org, May 11 2017

I think this is a dupe of  https://crbug.com/574442 , qinmin@, WDYT?

Comment 9 by qin...@chromium.org, May 11 2017

Mergedinto: 574442
Status: Duplicate (was: Untriaged)

Sign in to add a comment