+13
−5
Loading
6885: Issue #6884: SessionManager.onTrimMemory(): Do not remove engine session state from sessions. r=csadilek a=pocmo
When trimming memory we want to save the state of an engine session, attach it to the holder and close the engine session. Right now we try to do this for all sessions and then "unlink" them. This causes the engine session state to be cleared from sessions that either did not have an engine session (e.g. restored sessions) or that have been trimmed before. We should only perform this action for sessions that actually have an engine session. All other sessions can be left as-is.
Co-authored-by:
Sebastian Kaspari <s.kaspari@gmail.com>