Closed
Bug 896825
Opened 11 years ago
Closed 11 years ago
"Fix" bug 896776 in a way that is safe for leo
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Firefox OS Graveyard
Gaia::System
Tracking
(blocking-b2g:leo+, b2g18 fixed, b2g-v1.1hd fixed)
RESOLVED
FIXED
blocking-b2g | leo+ |
People
(Reporter: khuey, Assigned: khuey)
References
Details
(Whiteboard: [MemShrink:P1][LeoVB+])
Attachments
(1 file)
+++ This bug was initially created as a clone of Bug #896776 +++ What I really want to do in bug 896776 is probably too invasive for leo. So let's do something simpler.
Assignee | ||
Comment 1•11 years ago
|
||
Pointer to Github pull-request
Assignee | ||
Updated•11 years ago
|
Attachment #779594 -
Flags: review?(alive)
Assignee | ||
Updated•11 years ago
|
blocking-b2g: --- → leo?
Updated•11 years ago
|
Attachment #779594 -
Flags: review?(alive) → review+
Comment 3•11 years ago
|
||
As I said I'm working on a new system to resolve this kind of problems. I want to know: * The problem is closeCallback isn't reset to null or isn't invoked? * How if we have a static closeCallback for each frame and won't modify that callback after transition?
Assignee | ||
Comment 4•11 years ago
|
||
(In reply to Alive Kuo [:alive][Paris work week 7/22-26] from comment #3) > As I said I'm working on a new system to resolve this kind of problems. > I want to know: > * The problem is closeCallback isn't reset to null or isn't invoked? It is not invoked. closeCallback calls removeFrame, and if it is never invoked the iframe is never removed from the DOM. > * How if we have a static closeCallback for each frame and won't modify that > callback after transition? We need to ensure that we invoke the callback. That is the real problem here.
Comment 5•11 years ago
|
||
Yeah I know this problem...sigh it's not totally resolved by some workaround. So I'm working a brand-new transition control to fix all this kind of problems. Thanks for investigation.
Comment 6•11 years ago
|
||
> How about if we have a static closeCallback for each frame and won't modify that callback
> after transition?
That could work, but you would have to be careful not to leak closeCallback, because closeCallback would probably keep the iframe alive.
Comment 7•11 years ago
|
||
In bug 896776 Alive says he has a plan to change a lot of code so as to fix this on master. That's great, but then I think we should land this on master as well as b2g18, so both trees are leak-free.
Comment 8•11 years ago
|
||
(In reply to Justin Lebar [:jlebar] from comment #7) > In bug 896776 Alive says he has a plan to change a lot of code so as to fix > this on master. That's great, but then I think we should land this on > master as well as b2g18, so both trees are leak-free. Sure!
Updated•11 years ago
|
Whiteboard: [MemShrink] → [MemShrink:P1]
Comment 9•11 years ago
|
||
Pushed to master: https://github.com/mozilla-b2g/gaia/commit/3d64d2aefaa80919d183c95c2fd95a94f2b7702a
Assignee | ||
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Whiteboard: [MemShrink:P1] → [MemShrink:P1][LeoVB+]
Comment 10•11 years ago
|
||
Uplifted 3d64d2aefaa80919d183c95c2fd95a94f2b7702a to: v1-train: 25c7466682f1148da685abc1f2177a3221290d84
status-b2g18:
--- → fixed
Comment 11•11 years ago
|
||
v1.1.0hd: 25c7466682f1148da685abc1f2177a3221290d84
status-b2g-v1.1hd:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•