1007968 - [Tarako][email] attaching a large email and removing and repeating this will cause the email + other app to LMK

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::E-Mail, defect)

Description

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Attachment: email_attachment.log

Gaia      8969848adfdd8b0cfdfdf072f99b20505385482c
Gecko     https://hg.mozilla.org/releases/mozilla-b2g28_v1_3t/rev/1d997ccbf79c
BuildID   20140508014002
Version   28.1
ro.build.version.incremental=eng.cltbld.20140508.050145
ro.build.date=Thu May  8 05:01:52 EDT 2014
Tarako

1. launch email
2. setup email if you haven't
3. compose email
4. select attachment
5. select music
6. select a 3 MB mp3 for faster repro
7. delete the attachment
8. repeat 4 through 7 several times

Expected: you can keep doing it
Actual: memory doesn't release in step 7 so it LMKs both email and mail app

Note:
1. need to check 1.3+?

Comment 1

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

I can't seem to repro on 1.3 buri

Comment 2

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Currently I'm not sure of a practical application other than an indecisive person, who picks 3 different files before it ends up LMKing on them.

Comment 3

[Andrew Sutherland [:asuth] (he/him)]

Like most of the other similar email bugs, this is mainly a question of garbage collection as far as I can tell.  The email app does not do anything special to hold onto memory.  We do attach/detach attachments asynchronously, so if any of the attachments are memory-backed Blobs, those will increase peak memory usage.  But that does not seem to be the case here.

A complicating factor may be that all of the media apps that like to show previews are actually creating the <audio>/<video> tag to preview the Blobs before returning them.  This presumably causes the blobs to be opened/pre-buffered/etc./etc. which can increase system peak memory usage.

In general I don't think there's anything further we can do about this for v1.3T.  I propose we leave this bug open for triage/duping purposes until 1.3T gets closed out and then we invalid this and its friends out.  (In general we want to file actionable investigation bugs about reducing memory in certain spots, but we already have actionable bugs, they're just not actionable for v1.3T and most of them depend on platform bugs.)

Comment 4

[BMO Automation]

Firefox OS is not being worked on