[1.Description]: [Flame][v3.0][Music]About 1 second after "Create ringtone" view pops up, user will have no time to play or save the song in "Create ringtone" view because Settings app quits automatically and then it backs to homescreen. Found at: 13:09 Attach: logcat_1309.txt and music.3gp. [2.Testing Steps]: Prerequisite: Have some songs in device. 1. Go to Settings->Sound->Manage Tones. 2. Tap "+" icon and select a song as ringtone. 3. Tap "Done". [3.Expected Result]: 3. Settings app should not quit automatically when you add a song as ringtone, and the song can be added as ringtone successfully. [4.Actual Result]: 3. About 1 second after "Create ringtone" view pops up, Settings app will quit automatically, then you have no time to play/save the song in "Create ringtone" view, meanwhile the song can not be added as ringtone successfully. [5.Reproduction build]: Device: Flame v2.2 build(unaffected) Build ID 20150614002504 Gaia Revision cfceba16e48ede3defee24be93637a0fa291c494 Gaia Date 2015-06-11 22:10:18 Gecko Revision https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/2cfd86c2ba1b Gecko Version 37.0 Device Name flame Firmware(Release) 4.4.2 Firmware(Incremental) eng.cltbld.20150614.040237 Firmware Date Sun Jun 14 04:02:49 EDT 2015 Bootloader L1TC000118D0 Device: Flame v3.0 build(affected) Build ID 20150614010203 Gaia Revision 1bf2da102560481748ff3f6202fbed5c4daa5832 Gaia Date 2015-06-13 00:22:05 Gecko Revision https://hg.mozilla.org/mozilla-central/rev/c223b8844264 Gecko Version 41.0a1 Device Name flame Firmware(Release) 4.4.2 Firmware(Incremental) eng.cltbld.20150614.044513 Firmware Date Sun Jun 14 04:45:25 EDT 2015 Bootloader L1TC000118D0 Device: Nexus 5 v2.2 build(unaffected) Build ID 20150614002504 Gaia Revision cfceba16e48ede3defee24be93637a0fa291c494 Gaia Date 2015-06-11 22:10:18 Gecko Revision https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/2cfd86c2ba1b Gecko Version 37.0 Device Name hammerhead Firmware(Release) 5.1 Firmware(Incremental) eng.cltbld.20150614.042607 Firmware Date Sun Jun 14 04:26:25 EDT 2015 Bootloader HHZ12d Device: Nexus 5 v3.0 build(unaffected) Build ID 20150614010203 Gaia Revision 1bf2da102560481748ff3f6202fbed5c4daa5832 Gaia Date 2015-06-13 00:22:05 Gecko Revision https://hg.mozilla.org/mozilla-central/rev/c223b8844264 Gecko Version 41.0a1 Device Name hammerhead Firmware(Release) 5.1 Firmware(Incremental) eng.cltbld.20150614.044149 Firmware Date Sun Jun 14 04:42:08 EDT 2015 Bootloader HHZ12f [6.Reproduction Frequency]: Always Recurrence,5/5 [7.TCID]: Free Test [8.Note]: 1. If you quickly tap "Save" when the "Create ringtone" view pops up, the song can be added as ringtone successfully. 2. There is no crash log in device.

@Shally, I cannot reproduce this bug. Could you provide the music file in your test?

This probably belongs to the ringtones app because I saw the last app is ringtones.

Hi Hermes, I am able to reproduce this bug using some different MP3 files on different Flame devices, and upload two ".mp3" files for your reproduction. Thanks.

I still cannot reproduce... NI Ringtones developer for further investigation.

I can't reproduce this either.

Shally, Could you try to find out the different steps or configures between our tests? Maybe we can find the root cause. I used a fresh phone and then adb push some songs into my device. Then, follow "Testing Steps" at comment 0. Besides, I didn't do any configure change to my phone.

Hi Hermes, I still can repro this bug on 319mb mem (rate: 100%) by the STR in Comment 0, but can't repro it on 512mb/1024mb mem (rate: 0/10). Thanks

@Jim, per comment 10, could you try 319MB setting?

Well, I believe that it'd OOM on 319MB, but there's not much I can do about it (at least not without more info). Since almost nothing in the Create Ringtone activity has changed from 2.2 to 3.0, I'd have to guess that there's a memory regression in Gecko somewhere. A regression window would make this a lot more manageable. (Do we even need to test against 319MB anymore?)

Memory related issues are being tracked in bug 1162535. We can't do regression windows on memory/performances issues because the window will be inaccurate. > (Do we even need to test against 319MB anymore?) That is a good question and I want to ask that as well. But until we (QA) are told otherwise, we stay on 319MB of Flame.

Firefox OS is not being worked on