Idle AppCode 3.1.5 CPU usage

Hi guys,

I have a small project opened in a workspace. And that's all, there is no activity in the app while CPU usage is unreasonably high as shown on a picture below:

https://photos-2.dropbox.com/t/2/AAD1s60gXyRI9KIvZ7U1YnoWUCVdtQtlyP7hF_Oki1nfDg/12/60308511/png/32x32/3/_/1/2/Screenshot%202015-05-12%2020.11.38.png/CJ_44BwgASACKAE/YuFKgek_S_q2WQJ2-dnkOS0Mli3GXW_IfRsA210YCko?size=1024x768

This issue occurs randomly. I'm relatively new to OS X stuff and iOS development overall, may be the issue is in my setup, I dont know. BTW I have pretty much similar issue with Vagrant/VirtualBox when I suspend a virtual machine and then run it again.

Any info would be much appreciated. Thanks to all!

15 comments

Hi Ivan.

There are some problems with screenshots, so I can't see them.

Could you send your screenshots and also please capture a CPU snapshot how it described in the article and send it to appcode-support @ jetbrains.com?

0

Hi,

I think this may be the same issue I'm seeing.
I'm on 3.1.7, but it's been happening in earlier versions as well.

Basically any editing (even as small as a single character) will cause AppCode to consume 100-300% CPU (I'm on a MacBook Air with a 1,7 GHz Intel Core i7, 4 cores).
Depending on something (how much editing I'm doing?) this CPU usage can last for a very long time, effectively draining my battery quite fast, since I'm doing a fair bit of editing when coding :)

I've attached a CPU snapshot of this happening, from just before I started editing to just after I stopped typing and let the CPU usage go back down.

This is currently my main gripe with AppCode, as I'm travelling and am not always able to be connected to wall power.

Please let me know if I can provide more information or more snapshots!

Cheers,
--anders



Attachment(s):
OC-139.1402_anders_26.06.2015_18.13.44.zip
0

I am seeing 100% CPU usage in an idle AppCode 3.1.7, indefinitely as far as I can tell.  No background processes.

There seem to be about a dozen bug reports about this.  Does somebody need more info?

Nicholas

0

Hi!

Thank you for the snapshot!
We have found some problems with inspections.
Could you please try to disable some inspections (Preferences | Editor | Inspections) and have a look if it could help?
If yes, please specify which inspections you turned off?
Also if you could share a project with us or could send us a sample project it would be perfect!
You could send the project to appcode-support at jetbrains.com.

0

Hi Nicholas.

Coulde you please capture a CPU snapshot how it described in the article so we can take a look at what is going on?
The problems with high CPU usage could have different causes, so the best way to investigate them is to capture a snapshot.

0

Yes, I'd like to help, but I need more info.  I made a copy of appcode.vmoptions and added the line as requested in that document, and indeed I get the new menu items.  I chose Start CPU Usage Profiling, then later Stop CPU Usage Profiling.  What now?  Did it create a file at some well-known (to everyone but me) place, or was I supposed to be asked where I would like a file to get created?

By the way, I have discovered that this high CPU usage is *not* constant after all.  It seems to vary, but sometimes it only lasts for 20 seconds.

0

Oh, silly me -- I had the window partially off-screen, so I missed the notification.

I uploaded the file, OC-139.1402_nsterling_13.07.2015_01.38.03.zip (4.8 mb), at uploads.jetbrains.com.

I was not doing anything at all in AppCode the entire time, although surely the cursor entered and left the window multiple times.

This is a MacBook Pro (early 2011, Core i7) with 16 GB RAM running Yosemite.

Hope that helps!

Nicholas

0

By the way, I eventually discovered that the instructions on the "Reporting performance problems" page *do* say that a file gets created automatically in your home directory, but they say so in the section on Profiling Slow Startup.  Since that info presumably applies to all instances of profiling, perhaps it should be moved up toward the top?

0

Hi Anna.  Did you learn anything from that CPU snapshot from a week ago?  I am trying to use XCode in the meantime, but it hangs on me all the time, so I'm looking forward to AppCode working reasonably....

Nicholas

0

Hi Nicholas.

We've analyzed your snapshot, but it seems to be quite allright.
So, probably, the problem relates to the IDEA-126337 issue. Please stay tuned.

0

Thanks for checking, Anna.  I will (anxiously) await a fix.

Nicholas

0

This is really annoying me again.

Disabled _all_ inspections and set the file's highlighting mode to "syntax" instead of "inspections", closed all but two files, and still had 100% CPU usage for hours on end.
Doesn't even seem related to editing a file, as it just never goes down.

Since this still hasn't been fixed, I captured another profile dump, which is attached.
Hopefully that helps, and hopefully you give this issue some priority and release a fix soon.



Attachment(s):
OC-139.1402_anders_09.08.2015_01.14.56.zip
0

Hi.

Thank you for the details and sorry for the inconvenience!
After the investigation we suppose that the problem relates to the issue about Netty.
Please comment it or upvote.

0

I upgraded to the 141.2454 EAP released last night and I haven't seen this issue after running it for a few hours. Maybe it's been fixed?

0

Hi again.

So with 3.2, the biggest issues seem to have been reduced. In particular the perpetually high CPU usage is gone for me, which is nice. What I mean by that is that even though CPU usage spikes a lot, it does go back down fairly quickly.
It's on an acceptable level for me most of the time, but I do have major issues still with CPU usage in larger files.

I have one .cpp file which is ~3500 lines (why it's so big has its reasons), and it's basically impossible to work with it in AppCode 3.2.
In my opinion, nothing should come in the way of being able to edit a file, and in this file (and other larger files) the UI completely freezes while its doing "background" tasks.

Anyway, I've attached a CPU profile capture of this happening. What I did was open this large file; wait until AppCode CPU usage was low (below 10%); start the capture, and then hit Enter to insert a single new line.
I was going to let the capture run until CPU usage was back below 10%, but it took too long, so I stopped it anyway.

Hopefully it contains some useful information for you, in case you want to try to fix this issue.
The capture was too big as a .zip, so I recompressed it with 7z, hope that's OK!
Let me know if you want me to provide any more information/captures.



Attachment(s):
OC-141.2456_anders_07.09.2015_20.26.31.snapshot.7z.zip
0

Please sign in to leave a comment.