Description: When the user leaves the Message app from the New message screen and re-enters by edge gesture, sometimes the main Message app screen is displayed, not the New message screen. This issue also reproduces with Contacts with Add contact screen. Repro Steps: 1) Update a Flame to 20150421010201. 2) Open Messages, and select the New message icon. 3) When the New message screen opens and the keyboard pops up, press the home button. 4) Open Contacts app, and select the "+" icon. 5) Tap on any field to bring the keyboard. 6) Switch back and forth between Contacts and Messages by edge gesture a few times. Actual: The main Messages or Contacts app screen is displayed. Expected: The app always stays on the screen where the user was on previously. Environmental Variables: Device: Flame 3.0 (KK, 319mb, full flash) Build ID: 20150421010201 Gaia: a8e4f95dce9db727dda5d408b038f97fb4296557 Gecko: 7b823253d9f2 Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b 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 https://youtu.be/SMvl_ZwHbOI

This issue does NOT reproduce on Flame 2.2. Result: New message or Add contact screen always re-appears when re-entering the app by edge gesture. Environmental Variables: Device: Flame 2.2 (KK, 319mb, full flash) Build ID: 20150421002501 Gaia: 828dd03a0e3b140d74b2e49355197df4d91d9227 Gecko: 36f72a3efb9b Gonk: ebad7da532429a6f5efadc00bf6ad8a41288a429 Version: 37.0 (2.2) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Etienne, any idea whats going on?

[Blocking Requested - why for this release]: The user will also lose any data that they have entered so nominating this 3.0? Let's get a regression window here.

I'm blocked during this issue on because bug 1133111 seems to occur nearly every edge gesture following these steps back in February. The window is too wide to even do swaps on (the builds will not load when attempted, so I'm blocked. If someone else wants to give this a shot that would be great, or maybe someone will have some suggestions to circumvent the black screen edge gesture issue. Last Working Environmental Variables: Device: Flame 3.0 BuildID: 20150131033835 Gaia: 45475198737a504d81932a9c90002902054fce23 Gecko: 5cbae82bdb4b Version: 38.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:38.0) Gecko/38.0 Firefox/38.0 First Broken Environmental Variables: Device: Flame 3.0 BuildID: 20150218002006 Gaia: 82f286f10a41aab84a0796c89fbefe67b179994b Gecko: 9696d1c4b3ba Version: 38.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:38.0) Gecko/38.0 Firefox/38.0

Removing my name from this so someone else can know to take it.

(In reply to Gregor Wagner [:gwagner] from comment #2) > Etienne, any idea whats going on? Looks like the apps are just getting killed. If you uncheck "App Suspending" in the Developer settings the app should just go away instead (ie. nothing to swipe on)

I was also blocked by bug 1133111 and unable to get a narrower window. I've tried the following builds, which all displayed the black screen after edge gesture, which makes it impossible to determine whether the build is working or broken: BuildID: 20150131085436 > black screen BuildID: 20150201091835 > black screen BuildID: 20150204050406 > black screen BuildID: 20150207085528 > black screen BuildID: 20150211130440 > black screen BuildID: 20150213092459 > black screen BuildID: 20150217183533 > black screen

Is this a 319mb only issue?

(In reply to Gregor Wagner [:gwagner] from comment #8) > Is this a 319mb only issue? Yes. I can't reproduce this issue on unrestricted memory Flame (memory set to auto). Repro rate is 0 out of 20 attempts. Device: Flame (KK, full flashed, unrestricted memory) BuildID: 20150506010204 Gaia: 3e6fd1e0a478af2c95d09ce95c2c6de2de2fec14 Gecko: ba44099cbd07 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

Not blocking on low-mem regressions.

Firefox OS is not being worked on