Description: If the user edge gestures from the browser back to a picture that they are currently cropping in the gallery, the gallery app will force close. Repro Steps: 1) Update a Flame to 20150504010202. 2) Open Gallery. 3) Tap on a picture to open it. 4) Tap on the "Edit" icon. 5) Tap on the "Crop" icon. 6) Tap the home button on the phone and open the browser. 7) Edge gesture from the browser page back to the crop screen. Actual: The gallery app will force close if the user edge gestures from the browser to the crop screen. Expected: The user can edge gesture from the browser back to a picture they are currently cropping without issue. Environmental Variables: Device: Flame 3.0 (KK, 319mb, full flash) Build ID: 20150504010202 Gaia: e18cce173840d6ff07fb6f1f0e0ffb58b99aab3e Gecko: dc5f85980a82 Gonk: a9f3f8fb8b0844724de32426b7bcc4e6dc4fa2ed Version: 40.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0 Repro frequency: 5/5 See attached: video clip, logcat

Issue does NOT reproduce on Flame 2.2 The user can edge gesture from the browser back to a picture they are currently cropping without issue. Device: Flame 2.2 Build ID: 20150504002502 Gaia: 8d14361337e608c8cdf165ea5034db5eda23b618 Gecko: cb7cb6597c91 Gonk: a9f3f8fb8b0844724de32426b7bcc4e6dc4fa2ed Version: 37.0 (2.2) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0 Seeing different results on Flame 3.0. On repro, often the Browser is the app that force closes instead of the Gallery app.

Youtube video link showing issue: https://youtu.be/fdh-9ofv5lI

Does this only happen on 319MB devices?

It appears so. I cannot get this to occur when I set the Flame's memory to 512mb. The gallery app does not force close when edge gesturing to the crop screen from the browser.

[Blocking Requested - why for this release]: Performance regression. Requesting a window.

Repro rate for this bug dips and rises seemingly at random. After extensive investigation it has been determined that the bug occurs on builds as far back as 2.1 on Jellybean base. In addition to the repro rate varying between builds other issues such as the gallery screen going completely black and unresponsive and the inability (on earlier jb builds) to run two apps at once make it appear to be impossible to find even a central regression window for this 319 memory bug. Last Mozilla-Central Jellybean build with solid repro rate (3/5) of issue: Device: Flame 2.1 Jellybean (319MB) BuildID: 20140828132252 Gaia: 007f3c50cf69f044628a23c2376c6d88aa45f617 Gecko: d697d649c765 Version: 34.0a1 (2.1) Firmware: v123 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Not blocking on low-mem regressions.

Firefox OS is not being worked on