810686 - Keyboard's windows uses memory even after keyboard is closed. - We should release the keyboard window

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Gaia::System, defect)

Comment 1

[Andrea Marchesini [:baku]]

https://bugzilla.mozilla.org/show_bug.cgi?id=797203#c19
follow up

Comment 2

[Tim Guan-tin Chien [:timdream] (please needinfo)]

Reviving old bug -- this can be consider fixed once bug 942790 is fixed.

Comment 3

[Tim Guan-tin Chien [:timdream] (please needinfo)]

I am sorry, the original description was "closed", not "killed". So it's unrelated to OOM etc.

We tried not to kill the keyboard app as soon as it hides because the current launch time is still to long.

Comment 4

[Dietrich Ayala (:dietrich)]

Tim, is there something actionable here still?

Comment 5

[[:fabrice] Fabrice Desré]

Looks similar to what I'm doing in bug 957880

Comment 6

[Nicholas Nethercote [inactive]]

(In reply to Tim Guan-tin Chien [:timdream] (MoCo-TPE) (please ni?) from comment #2)
> Reviving old bug -- this can be consider fixed once bug 942790 is fixed.

So can we close this?

Comment 7

[Tim Guan-tin Chien [:timdream] (please needinfo)]

(In reply to Nicholas Nethercote [:njn] from comment #6)
> (In reply to Tim Guan-tin Chien [:timdream] (MoCo-TPE) (please ni?) from
> comment #2)
> > Reviving old bug -- this can be consider fixed once bug 942790 is fixed.
> 
> So can we close this?

With bug 942790 the keyboard app will now subject to OOM just like any other apps. However we still launch a keyboard in the background during boot, so you could say this bug is fixed, depend on the perspective.

To NOT launch the keyboard during boot-up, we could turning on bug 956269 by default. The user experience will be affected by cold launch speed of the keyboard through.

:njn, you could close this bug if you think our current progress (bug 942790 and bug 957880) fix the behavior (on v1.4 and v1.3, respectively).