Closed
Bug 1686037
Opened 4 years ago
Closed 4 years ago
leak on layout/base/tests/test_bug993936.html with implicit pointer capture enabled
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P3)
Core
DOM: UI Events & Focus Handling
Tracking
()
RESOLVED
FIXED
86 Branch
Tracking | Status | |
---|---|---|
firefox86 | --- | fixed |
People
(Reporter: edgar, Assigned: edgar)
References
Details
Attachments
(3 files)
Bug 1682527 was backed out due to there is a leak in https://searchfox.org/mozilla-central/source/layout/base/tests/test_bug993936.html.
Assignee | ||
Comment 1•4 years ago
|
||
The test synthesizes touchstart
and touchmove
event, but no touchend
. And it seems the PointerCapture isn't released properly due to the leak of touchend
event.
Assignee | ||
Comment 2•4 years ago
|
||
Assignee | ||
Comment 3•4 years ago
|
||
Depends on D102321
Assignee | ||
Comment 4•4 years ago
|
||
Depends on D102403
Assignee | ||
Comment 5•4 years ago
|
||
Updated•4 years ago
|
Attachment #9198134 -
Attachment description: Bug 1686037 - Part 3: Remove redundant ImplicitlyReleasePointerCapture call in PresShell; → Bug 1686037 - Part 3: Remove duplicated ImplicitlyReleasePointerCapture call in PresShell;
Assignee | ||
Comment 6•4 years ago
|
||
Pushed by echen@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/7e5ee5c59695 Part 1: Move nsGenericHTMLElement::GetPresContext to Element; r=smaug https://hg.mozilla.org/integration/autoland/rev/554546208c0b Part 2: Clean up pointer capture info when PresContext is destroyed; r=smaug https://hg.mozilla.org/integration/autoland/rev/8af0c61efbc5 Part 3: Remove duplicated ImplicitlyReleasePointerCapture call in PresShell; r=smaug
Comment 8•4 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/7e5ee5c59695
https://hg.mozilla.org/mozilla-central/rev/554546208c0b
https://hg.mozilla.org/mozilla-central/rev/8af0c61efbc5
Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox86:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 86 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•