Graphical Glitches and Screen Flickering in Full Screen
已回答
I am having extreme screen flickering whenever I interact with any type of menu in CLion or any other JetBrains IDE, but only when the app is in full screen mode. I'm using Manjaro with the I3 window manager. Here is a link to what it looks like:
请先登录再写评论。
Hi! Sorry for the inconvenience. Please send the idea.log file (Help | Show Log in ...) to clion-support at jetbrains.com. Note that logs might contain private user's information (like file paths and names). Additionally specify whether you use bundled JDK or custom. Thanks in advance!
I can confirm this issue. It's very annoying. The only way I can still use this IDE is by not using full screen mode completely which is stupid on tiling window managers.
vanilla Manjaro i3-community edition(arch linux)
latest stable RubyMine ver
Same issue. Partially solved by disabling Compton. But since it happens only with Jetbrains products, it's still very annoying.
After a little testing:
Flickering/screen tearing happens on all Jetbrains products.
Only happens if Compton is enabled and the IDE is in full-screen mode. Going to windowed solves the issue.
Please report the issue to the platform's tracker, since it happens in all JetBrains products: https://youtrack.jetbrains.com/issues/IDEA.
Same issue. I use manjaro with i3 tiling-window manager with picom (cause compton was outdated). I solved this issue by setting the follwing option in picom config (see: https://wiki.archlinux.org/index.php/Picom#Flicker)
same issue. CLion 2022.2.4, apple m1, Ventura 13.0
Kostas Maybe it's related to https://youtrack.jetbrains.com/issue/JBR-4680. Could you please try using the workarounds described in the issue? Does any of them help?
Having the same issue on my MacBook Pro M1, Ventura 13.0. Appears only when editing my code and program in fullscreen.
Hi all!
There is an issue - https://youtrack.jetbrains.com/issue/JBR-4959. It was partially fixed, but not all the cases are covered by the fix. The team continues the investigation.
There is a workaround described in the issue, please try using it:
add the following string into "Help | Edit Custom VM Options":