From 1645bcb5467487d63805742e8d98afcafb00577d Mon Sep 17 00:00:00 2001 From: Karol Lewandowski Date: Tue, 3 Dec 2024 11:27:03 +0100 Subject: [PATCH] disposers.md: Clarify enabling disposers debugging --- topics/basics/disposers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/topics/basics/disposers.md b/topics/basics/disposers.md index ad3a2ac1f..81c4f41da 100644 --- a/topics/basics/disposers.md +++ b/topics/basics/disposers.md @@ -232,7 +232,7 @@ Regardless, it illustrates the basic pattern, which is: When the application exits, it performs a final sanity check to verify everything was disposed. If something was registered with the `Disposer` but remains undisposed, the IntelliJ Platform reports it before shutting down. -In test and Debug mode (`idea.disposer.debug` is set to `on`), registering a `Disposable` with the `Disposer` also registers a stack trace for the object's allocation path. +In test, [internal](enabling_internal.md), and debug mode (add `idea.disposer.debug=on` in Help | Edit Custom Properties...), registering a `Disposable` with the `Disposer` also registers a stack trace for the object's allocation path. The `Disposer` accomplishes this by creating a `Throwable` at the time of registration. The following snippet represents the sort of "memory leak detected" error encountered in practice: