Closed
Bug 896776
Opened 12 years ago
Closed 7 years ago
window_manager.js should not use animation callbacks to dispose of app iframes
Categories
(Firefox OS Graveyard :: Gaia::System::Window Mgmt, defect)
Firefox OS Graveyard
Gaia::System::Window Mgmt
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: khuey, Assigned: alive)
Details
(Whiteboard: [MemShrink:P2])
window_manager.js has a complex system of callbacks to handle animation. These callbacks can be skipped in various situations when an animation is no longer needed for performance or correctness reasons. Unfortunately we're also using these callbacks for disposing of resources (such as removing app iframes from the DOM) and skipping a callback results in a leak. Either we need a separate callback system that is guaranteed to be called or we need to ensure that the animation callbacks are always called.
Assignee | ||
Comment 1•12 years ago
|
||
Kyle, thanks for filing this.
I'm working on a new system about right what you mentioned here.
See https://docs.google.com/file/d/0B8_DREosp7m2X3o4MFBqVzhkekU/edit?usp=sharing for reference, page 23.
Reporter | ||
Comment 2•12 years ago
|
||
Cool. Let me know if there's anything I can do to help.
Assignee: nobody → alive
Comment 3•12 years ago
|
||
Can we land bug 896825 on master as well as b2g18, so we at least fix the leak on all our trees?
![]() |
||
Updated•12 years ago
|
Whiteboard: [MemShrink] → [MemShrink:P2]
Comment 4•12 years ago
|
||
I'm clearing the blocking of bug 893012, because the leak problem was fixed on trunk and b2g18 via bug 896825.
No longer blocks: 893012
Updated•11 years ago
|
Component: Gaia::System → Gaia::System::Window Mgmt
Assignee | ||
Comment 5•11 years ago
|
||
I am confident this is resolved by bug 907013.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 6•10 years ago
|
||
The existence of bug 1050751 makes it clear that this is not fixed.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 7•10 years ago
|
||
I think the real problem is not "we should not remove iframe in transitionend callback".
Removing the iframe from DOM while it's container is still closing doesn't convince me.
The real issue is at certain case the removing will be canceled, but definitely what's described in the bug summary.
Comment 8•7 years ago
|
||
Closing out old Firefox OS specific memshrink bugs.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•