fix(gestures): separate unregister from delete to avoid use-after-free#1089
Open
deepin-wm wants to merge 1 commit into
Open
fix(gestures): separate unregister from delete to avoid use-after-free#1089deepin-wm wants to merge 1 commit into
deepin-wm wants to merge 1 commit into
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: deepin-wm The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Reviewer's guide (collapsed on small PRs)Reviewer's GuideIntroduces separate removal methods for swipe and hold gestures that decouple unregistration from object deletion to avoid use-after-free and circular destruction issues, and updates InputDevice to use the new APIs. Sequence diagram for updated gesture removal flowsequenceDiagram
participant InputDevice
participant GestureRecognizer
participant SwipeGesture
InputDevice->>GestureRecognizer: unregisterTouchpadSwipe(gesture)
GestureRecognizer->>GestureRecognizer: removeSwipeGesture(gesture)
GestureRecognizer->>GestureRecognizer: unregisterSwipeGesture(gesture)
GestureRecognizer->>SwipeGesture: deleteLater()
InputDevice->>GestureRecognizer: unregisterTouchpadHold(gesture)
GestureRecognizer->>GestureRecognizer: removeHoldGesture(gesture)
GestureRecognizer->>GestureRecognizer: unregisterHoldGesture(gesture)
GestureRecognizer->>HoldGesture: deleteLater()
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
deepin-wm
force-pushed
the
fix/gesture-use-after-free
branch
from
July 2, 2026 11:17
fe8c743 to
8fca0ab
Compare
unregisterSwipeGesture/unregisterHoldGesture previously called deleteLater() on the gesture object. This is dangerous because: 1. The QObject::destroyed signal handler also calls unregister, creating a circular dependency. 2. Callers may still reference the gesture after unregister. Add removeSwipeGesture/removeHoldGesture that call unregister then deleteLater, and update InputDevice callers to use the new methods. WM-29
deepin-wm
force-pushed
the
fix/gesture-use-after-free
branch
from
July 2, 2026 11:25
8fca0ab to
8bfafc6
Compare
|
TAG Bot New tag: 0.8.14 |
|
TAG Bot New tag: 0.8.15 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
unregisterSwipeGesture/unregisterHoldGesture previously called deleteLater() on the gesture object. This is dangerous because:
Add removeSwipeGesture/removeHoldGesture that call unregister then deleteLater, and update InputDevice callers to use the new methods.
Extracted from #1046. Ref: WM-29
Summary by Sourcery
Separate gesture unregistration from object deletion to avoid use-after-free issues in gesture handling.
Bug Fixes:
Enhancements: