From f93e22c84a6177977b689f3c147b2195e068027a Mon Sep 17 00:00:00 2001 From: Ying Li Date: Sat, 8 Mar 2025 16:37:59 +0900 Subject: [PATCH] fix for image width --- docs/topics/debug-coroutines-with-idea.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/topics/debug-coroutines-with-idea.md b/docs/topics/debug-coroutines-with-idea.md index 9ac49fddbb..1c48b558ff 100644 --- a/docs/topics/debug-coroutines-with-idea.md +++ b/docs/topics/debug-coroutines-with-idea.md @@ -108,7 +108,7 @@ Using IntelliJ IDEA debugger, you can dig deeper into each coroutine to debug yo If you use `suspend` functions, in the debugger, you might see the "was optimized out" text next to a variable's name: -![Variable "a" was optimized out](variable-optimised-out.png) +![Variable "a" was optimized out](variable-optimised-out.png){width=480} This text means that the variable's lifetime was decreased, and the variable doesn't exist anymore. It is difficult to debug code with optimized variables because you don't see their values. @@ -116,4 +116,4 @@ You can disable this behavior with the `-Xdebug` compiler option. > __Never use this flag in production__: `-Xdebug` can [cause memory leaks](https://youtrack.jetbrains.com/issue/KT-48678/Coroutine-debugger-disable-was-optimised-out-compiler-feature#focus=Comments-27-6015585.0-0). > -{style="warning"} \ No newline at end of file +{style="warning"}