Skip to content

fix(gestures): separate unregister from delete to avoid use-after-free#1089

Open
deepin-wm wants to merge 1 commit into
linuxdeepin:master-backup-20260717from
deepin-wm:fix/gesture-use-after-free
Open

fix(gestures): separate unregister from delete to avoid use-after-free#1089
deepin-wm wants to merge 1 commit into
linuxdeepin:master-backup-20260717from
deepin-wm:fix/gesture-use-after-free

Conversation

@deepin-wm

@deepin-wm deepin-wm commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

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.

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:

  • Fix potential use-after-free by ensuring swipe and hold gestures are only deleted after being cleanly unregistered from the recognizer.

Enhancements:

  • Introduce removeSwipeGesture and removeHoldGesture helpers that unregister and then schedule deletion of gesture objects, updating InputDevice to use these safer APIs.

@deepin-ci-robot

Copy link
Copy Markdown

[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.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@sourcery-ai

sourcery-ai Bot commented Jul 2, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Introduces 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 flow

sequenceDiagram
    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()
Loading

File-Level Changes

Change Details Files
Split gesture unregistration from object deletion to prevent use-after-free and circular destruction callbacks.
  • Stop calling deleteLater() inside unregisterSwipeGesture and unregisterHoldGesture.
  • Introduce removeSwipeGesture and removeHoldGesture that first unregister the gesture and then schedule it for deletion.
  • Ensure gesture cancellation continues to be emitted on unregistration before deletion.
src/input/gestures.cpp
src/input/gestures.h
Update InputDevice gesture cleanup to use the new removal methods.
  • Change unregisterTouchpadSwipe to call removeSwipeGesture instead of unregisterSwipeGesture.
  • Change unregisterTouchpadHold to call removeHoldGesture instead of unregisterHoldGesture.
src/input/inputdevice.cpp

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@deepin-wm
deepin-wm force-pushed the fix/gesture-use-after-free branch from fe8c743 to 8fca0ab Compare July 2, 2026 11:17
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
deepin-wm force-pushed the fix/gesture-use-after-free branch from 8fca0ab to 8bfafc6 Compare July 2, 2026 11:25
@deepin-bot

deepin-bot Bot commented Jul 10, 2026

Copy link
Copy Markdown

TAG Bot

New tag: 0.8.14
DISTRIBUTION: unstable
Suggest: synchronizing this PR through rebase #1123

@deepin-bot

deepin-bot Bot commented Jul 17, 2026

Copy link
Copy Markdown

TAG Bot

New tag: 0.8.15
DISTRIBUTION: unstable
Suggest: synchronizing this PR through rebase #1163

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants