diff --git a/microsoft-edge/devtools-guide-chromium/memory-problems/dom-leaks.md b/microsoft-edge/devtools-guide-chromium/memory-problems/dom-leaks.md index 97d94af4fb..04ab767054 100644 --- a/microsoft-edge/devtools-guide-chromium/memory-problems/dom-leaks.md +++ b/microsoft-edge/devtools-guide-chromium/memory-problems/dom-leaks.md @@ -6,10 +6,21 @@ ms.author: msedgedevrel ms.topic: conceptual ms.service: microsoft-edge ms.subservice: devtools -ms.date: 07/05/2023 +ms.date: 09/18/2023 --- # Debug DOM memory leaks with the Detached Elements tool +> [!IMPORTANT] +> The **Detached Elements** tool is being deprecated. Starting with Microsoft Edge 130, the **Detached Elements** tool has a message stating that the tool is deprecated; instead, in the **Memory** tool, in the initial **Select profiling type** screen, select the **Detached elements** option button. The Edge-only Chrome DevTools Protocol (CDP) function `EdgeDOMMemory.getDetachedNodesIds` continues to work, but use `DOM.getDetachedDomNodes` instead. +> +> In Microsoft Edge 133, the **Detached Elements** tool will be removed; instead, in the **Memory** tool, in the initial **Select profiling type** screen, select the **Detached elements** option button. The CDP function `EdgeDOMMemory.getDetachedNodesIds` will be removed; use `DOM.getDetachedDomNodes` instead. + + + Use the **Detached Elements** tool to find detached elements that the browser cannot garbage-collect, and locate the JavaScript object that is still referencing the detached element. By changing your JavaScript to release the element, you reduce the number of detached elements on your page. A memory leak can occur in your application when an element is no longer attached to the Document Object Model (DOM) tree, but is still referenced by some JavaScript running on the page. These elements are called *detached elements*. For the browser to garbage-collect (GC) the detached element, the element must not be referenced from the DOM tree or from JavaScript code.