launchd - high CPU usage - 90.94 and 90.116

On Mac OS X 10.6.1 I'm experiencing long-running launchd processes after upgrading to 90.94 and 90.116.  I had never seen this behavior on previous Maia EAP releases.

I'm not sure what the triggering behavior is.  But while editing Java files my IDE becomes unresponsive.  top shows that launchd is taking 90% of the CPU.  I don't know what IntelliJ is trying to ask my computer to do, but it renders the IDE unusable for 90-120 seconds when this occurs.

If you have suggestions on how I could instrument this better so you can isolate the root cause, please let me know.  This issue makes these last two EAPs extremely difficult for me to use during my daily work.

-- James



Attachment(s):
Screen shot 2009-10-26 at 10.57.55 PM.png
9 comments
Comment actions Permalink

Same here, last EAPs are more or less unusable after a while on Mac OSX - both due to performance and memory-leak problems (especially when having multiple projects open).

0
Comment actions Permalink

Jetbrains usually want to see CPU usage and memory snapshots in this situation.

YC> Same here, last EAPs are more or less unusable after a while on Mac
YC> OSX - both due to performance and memory-leak problems (especially
YC> when having multiple projects open).
YC>
YC> ---
YC> Original message URL:
YC> http://www.jetbrains.net/devnet/message/5248113#5248113


0
Comment actions Permalink

Same for 122 - unusable on Mac. "Updating indices" takes ages, after a few minutes of work IDEA becomes totally unresponsive.

0
Comment actions Permalink

That is unfortunately true for #9939 as well when multiple projects are opened.
Idea becomes very unresponsive.

On 2009-10-27 19:16:31 +0900, Yann Cébron <no_reply@jetbrains.com> said:

Same here, last EAPs are more or less unusable after a while on Mac OSX
- both due to performance and memory-leak problems (especially when
having multiple projects open).

---
Original message URL: http://www.jetbrains.net/devnet/message/5248113#5248113



0
Comment actions Permalink

It's too early to declare victory, but after ~2hours of running 90.122 things are working fairly well on my Mac.

How is 122 working for other Mac users out there?  The launchd issues I saw on 94 and 116 have not surfaced (yet).

-- James

0
Comment actions Permalink

Update on this with 90.137 on Mac OS 10.6.1.

I'm seeing the same launchd issues I originally reported.  They only happen on my largest Java project (2000+ .java files).  After about 15 minutes of usage, a launchd process is execute by IntelliJ, which renders the IDE unusable (spinny ball appears).  There is no status message in the IDE, so I'm not sure if it's indexing.  I have no idea what it's doing, but one of my CPU cores is 100% saturated, and the IDE is locked.

This behavior has not occurred on my smaller projects.  Unfortunately I need to spend today working on this large project, so I have to figure out a workaround (Emacs I suppose).

It would be excellent to understand what this launchd process is doing.  Let me know if I should open a Youtrack issue for this.  I also don't know how to get you guys better instrumentation of the problem, but I'm eager to get some fix or explanation for this behavior.  It appears to have started in 90.94.

-- James

0
Comment actions Permalink

I have a similar problem since 90.94 and still present in 90.137. I now start IDEA from terminal and set -XX:MaxPermSize=250m. With these settings I have only had one freeze so far. Before IDEA consistently froze after just a few minutes, even on smaller projects, except when I never compiled anything. So the problem seems to be related to compilation. Sometimes a PermGen error was reported on the console, at other times nothing was reported. Once IDEA froze, it never came back (I had to force quit).

0
Comment actions Permalink

Peter,

Thank you for that suggestion.  I have made this change to my Info.plist file and restarted IntelliJ.  Fingers crossed...

-- James

0

Please sign in to leave a comment.