Closed
Bug 1456260
Opened 6 years ago
Closed 6 years ago
Support concurrent GeckoSession.saveState() calls
Categories
(GeckoView :: General, enhancement, P1)
Tracking
(firefox61 fixed)
RESOLVED
FIXED
mozilla61
Tracking | Status | |
---|---|---|
firefox61 | --- | fixed |
People
(Reporter: droeh, Assigned: droeh)
Details
(Whiteboard: [geckoview:klar])
Attachments
(1 file)
2.95 KB,
patch
|
jchen
:
review+
|
Details | Diff | Splinter Review |
Currently we log a warning and return a null saved state if GeckoSession.saveState() is called while we are already in the middle of saving state; it would be better to fully support this case.
Updated•6 years ago
|
Assignee: nobody → droeh
Priority: -- → P1
Whiteboard: [geckoview+klar]
Updated•6 years ago
|
Whiteboard: [geckoview+klar] → [geckoview:klar]
Assignee | ||
Comment 1•6 years ago
|
||
Attachment #8971618 -
Flags: review?(nchen)
Comment 2•6 years ago
|
||
Comment on attachment 8971618 [details] [diff] [review]
Support concurrent saveState() calls
Review of attachment 8971618 [details] [diff] [review]:
-----------------------------------------------------------------
This is okay, though we should really only send one "GeckoView:SaveState" message at a time, and return the same state to all pending `saveState()` calls.
Please file a follow-up bug about cleaning up callbacks if the child disconnects unexpectedly, in which case we won't receive "GeckoView:SaveStateFinish".
Attachment #8971618 -
Flags: review?(nchen) → review+
Assignee | ||
Comment 3•6 years ago
|
||
(In reply to Jim Chen [:jchen] [:darchons] from comment #2)
> This is okay, though we should really only send one "GeckoView:SaveState"
> message at a time, and return the same state to all pending `saveState()`
> calls.
I thought about going this route, but isn't it possible for the state to have changed between when the two GeckoSession.saveState() calls are made?
Comment 4•6 years ago
|
||
It's all asynchronous so it doesn't really matter if the state changes in the meantime. Even in the current case, the state could have changed between the child sending the message and the parent receiving the response.
Assignee | ||
Comment 5•6 years ago
|
||
Fair enough. I'll address that in the follow up, as I'm on PTO next week and don't want to leave this hanging over a minor issue.
Pushed by droeh@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/62eb4b67db48
Support concurrent GeckoSession.saveState() calls. r=jchen
Pushed by droeh@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/f7289b97cdf1
Fix eslint failure. r=me
Comment 8•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/62eb4b67db48
https://hg.mozilla.org/mozilla-central/rev/f7289b97cdf1
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox61:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 61
Updated•6 years ago
|
Product: Firefox for Android → GeckoView
Updated•6 years ago
|
Target Milestone: Firefox 61 → mozilla61
You need to log in
before you can comment on or make changes to this bug.
Description
•