Skip to content

fix: memory leak#2463

Closed
SpanManX wants to merge 1 commit intoSortableJS:masterfrom
SpanManX:fix-memory-leak
Closed

fix: memory leak#2463
SpanManX wants to merge 1 commit intoSortableJS:masterfrom
SpanManX:fix-memory-leak

Conversation

@SpanManX
Copy link

In a low-code–like platform, elements from the left panel are dragged onto the canvas on the right to generate a component, and the dragged source element is removed. When the newly generated component is deleted, a memory leak occurs.

The multiDrag property is not properly checked, causing the following code to execute even when multiDrag is set to false:
delayStartGlobal({ dragEl: dragged }) { dragEl = dragged; }
1

When logging inside _onDrop, dragEl has already been removed from the DOM, but in MultiDrag.js, dragEl still retains a reference to the DOM node.
3

@SpanManX
Copy link
Author

@owen-m1 Please review my code.

owen-m1 added a commit that referenced this pull request Mar 24, 2026
@owen-m1
Copy link
Member

owen-m1 commented Mar 24, 2026

Thanks I've fixed it in a different way: 48b626b

@owen-m1 owen-m1 closed this Mar 24, 2026
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