Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 465e29d

Browse filesBrowse files
authored
Set a predefined image width in debug-coroutines-with-idea.md (#4377)
1 parent c08fa74 commit 465e29d
Copy full SHA for 465e29d

File tree

Expand file treeCollapse file tree

1 file changed

+2
-2
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+2
-2
lines changed

‎docs/topics/debug-coroutines-with-idea.md

Copy file name to clipboardExpand all lines: docs/topics/debug-coroutines-with-idea.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -108,12 +108,12 @@ Using IntelliJ IDEA debugger, you can dig deeper into each coroutine to debug yo
108108

109109
If you use `suspend` functions, in the debugger, you might see the "was optimized out" text next to a variable's name:
110110
111-
![Variable "a" was optimized out](variable-optimised-out.png)
111+
![Variable "a" was optimized out](variable-optimised-out.png){width=480}
112112
113113
This text means that the variable's lifetime was decreased, and the variable doesn't exist anymore.
114114
It is difficult to debug code with optimized variables because you don't see their values.
115115
You can disable this behavior with the `-Xdebug` compiler option.
116116

117117
> __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).
118118
>
119-
{style="warning"}
119+
{style="warning"}

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.