Why is CLion caught on M1 professional



Just lately I discovered the CLion is just a little caught in M1 professional chip. Why did this occur? is there anyway to resolve this drawback? The CLion model is:

CLion 2022.1.2
Construct #CL-221.5787.29, constructed on June 1, 2022
Licensed to cruise-open / jiang xiaoqiang
Subscription is energetic till April 20, 2023.
For non-commercial open supply growth solely.
Runtime model: 11.0.15+10-b2043.56 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 12.4
GC: G1 Younger Technology, G1 Outdated Technology
Reminiscence: 2000M
Cores: 10

Non-Bundled Plugins:
    org.rust.lang (
    ru.adelf.concept.dotenv (2022.1)

Is anybody dealing with the same drawback? I am utilizing macOS Monterey 12.4. I set up the CLion utilizing App Toolbox, I feel it’s the mac M1 model of CLion as a result of the runtime: Runtime model: 11.0.15+10-b2043.56 aarch64.



Please enter your comment!
Please enter your name here