here's a process dump from activity monitor in case it might help...

note: the dump shows the open files and ports used by IDEA 7.0.1 process

I did the following checks to isolate the source of this error:

• I reinstalled a fresh copy of IDEA 7.0.1.app -> no effect
  
• I removed Library/Preferences/IntelliJIDEA70 -> no effect
  
• I removed Library/Application Support/IntelliJIDEA70 -> no effect
  
• I removed Library/Caches/IntelliJIDEA70 -> no effect
  
• I tried -d32 and -d64 (32bit vs. 64 bit mode) in the vmoptions for java runtime in Info.plist -> no effect
  
• I tried the -server option in the vmoptions for java runtime in Info.plist -> no effect
  
• I created a new project being just empty with not even a single java class inside -> no effect, still broken (maybe it's the up-to-date-check that causes this issue ?)
  
  

This problems seems to happen whenever the IDE is launching the compiler, or maybe just checking the dependencies -> the number of threads from IDEA's process does not increment, just the load gets higher around 0.5 - 1.0 % percent every time.

after 30-60 compiles it's not acceptable to continue work as the base load is around 30-40 % which is just too high!

the mac os version is 10.5.1 (most current as up to now)

I renamed 'fslogger' to prevent idea from starting it, still there...

verified the above for selena-7562 which is still broken...

still there in selena-7573

I found out that the situation only arises when I choose Look-And-Feel = Mac OS

Once I choose for example Alloy it disappears...

Peter,

Please take a CPU snapshot. Unfortunately there's no useful information in the process dump.

How do you take a CPU snapshot, please?

ok, found it...

This is strange because this problem (which is actually in the Apple JDK implementation) is supposed to be fixed in Leopard. We'll see what we can do.

I did a fresh install of Leopard and did not modify my JVM in any way... It should be a typical out-of-the-box installation:

$ java -version
java version "1.5.0_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-237)
Java HotSpot(TM) Client VM (build 1.5.0_13-119, mixed mode, sharing)

Just wanted to report that in Selena-7626 this look-and-feel is as broken as before. So 'Mac OS X' and 'QuaQua' is currentlly unusable on Leopard. Makes it look a lot like Eclipse when switching off that themes. Sad! :-(

I believe that I am experiencing the same issue. Is there something I can do to help with debugging?

It's been six weeks now, I tried to give you as much information as possible and all you say is 'we see what we can do'

I am a paying customer and it wouldn't be too much to give us feedback on this issue. I understand you have plenty of issues to solve but some feedback would be nice.

Are you able to reproduce the situation? Are you working on it?

Not being able to use Mac OS Look and Feel on a Mac does really suck and we all want to "develop with pleasure" ...

As long as this and other Mac OS X related issues are not fixed I will NOT upgrade to v7.x !!!

Could this be caused by a JProgressBar leak?
I have uploaded "7718_bas_28.02.2008_16.48.23.zip" to ftp.intellij.net/.uploads. This memory snapshot was taken after closing all projects. It contains 274 JProgressBars and on OS X JProgressBars each take a little cpu because of the animation even if it is not progressing. (it also contains three leaked projects and some other leaks that might be interesting).
Choosing a different look and feel might be a workaround for this problem, but I have not yet tested that.

Further research suggests the progress bar leak is caused by the apple look and feel.

As far as I remember this happens to me when using Look and Feel

• Mac OS X
  
• QuaQua
  
  

so like you say it's obviously caused by Apple's look and feel.

Currently I work with the 'Bedoin' theme but it's really ugly on OS X :-(

Good to see this issue is gaining some momentum as we apple fanboys get anal quickly when something looks different than our beloved OS X g

I checked the issue on the java 6 developer preview 9 from apple (using IDEA_JDK and idea.sh) and figured out the problem still exists. it will obviously not disappear when java 6 is released final on mac but it's probably a bug in IDEA.

five month, nothing happening, just great!

When starting IntelliJ and opening my project it uses already about 5% CPU while idling. No other software on my Mac exhibits this kind of CPU usage when doing nothing. After extended use CPU usage climbs to 20% and above while idling. This severly limits my ability to develop on my MacBook without being connected to power. Why isn't anything done about this?

Seems like Mac OS X doesn't count much at IntelliJ -- even Eclipse support (which is unpaid) is more responsive than that :-(

I'm having the same problem. A day after a fresh restart, IntelliJ idles at about 30% CPU on a Macbook Core Duo 2 running at 2Ghz. So I'm restarting IntelliJ every day to keep my computer cool.

If the JProgressBar animation (on Mac OS X LnF) is causing this 'CPU leak', an easy workaround would be to disable the progress bar animation. You can do that by setting the following property :

javax.swing.UIManager.put("ProgressBar.repaintInterval", new Integer(Integer.MAX_VALUE));

I've been using this in muCommander after noticing JProgressBar was a real CPU hog and it works like a charm. It'd be worth trying this given the severity of this issue.

Note that this is the only serious problem I'm having with IntelliJ under OS X, which otherwise is an amazing product that I'm recommending all the time. Thank you guys for the hard work!

Same problem for me. Latest OSX and standard JVM.

Seems like this still continues with the new 1.6 JDK Apple just released, under Leopard.

Been trying this with the latest versions of Java6 and IDEA as they have become available since I first experienced this problem in November last year.

I have been a pretty solid supporter of IDEA for a few years but this degree of abandonment of an entire OS user base (over 5 months without so much as a "we expect a fix in releasse ????") is shithouse customer support. I'm finding IDEA a bit of a hard-sell in my office thanks to stuff like this. Really unimpressive guys.

Just a friendly reminder : I have included a potential fix in my previous comment. It should take 5 minutes to find out if that fixes the problem or not.

Try waiting for another 6-12 months and maybe someone will care...

Priority: critical, Severity: extreme, Countermeasures: none

it looks like this problem is gone with latest jdk1.5 update, progresses now reset timers correctly

I tried many re-builds (>30) in a row and after all idea consumes around 2-5% of cpu (by activity monitor)

please feedback on this if the problem still exists on your side

Thanks for looking into it. The problem is however still here for me with IntelliJ 7.0.3 after the 'Java for Mac OS X 10.5 Update 1' : IntelliJ idles in the background at 20% CPU usage not even a day after I last started it.

I noticed the idle CPU usage increases a lot after I switch projects (File -> Reopen), maybe because a lot of progress bars are displayed while the project is being loaded.

Feel free to let me know if you need any more information from me to reproduce the problem.

Alternatively, you can create a build with the afore-mentioned fix (see my previous comments) and I'll let you know if the problem is solved.

Please let me know of your java -version, just in case.

$ java -version
java version "1.5.0_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-237)
Java HotSpot(TM) Client VM (build 1.5.0_13-119, mixed mode, sharing)

Additional information:

IntelliJ 7.0.3 (build #7757)
Mac OS X 10.5.2
Macbook Core 2 Duo 2 GHz

I found the problem and sent its description to people in Apple. The workaround is possible, so I will put it both in IDEA 7.0.4 and 8.x.

FYI, this is what I sent to Apple:

Setting the progress to 100% didn't work for us. After some investigation I found that the progress's UI class (CUIAquaProgressBar) contains a bug that makes IDEA leak CPU time.

CUIAquaProgressBar starts the animation timer on new JProgressPane() but stops it when the progress is taken out of the component tree. More correct behavior would be to make this symmetric: to start the timer when the progress is put to the tree and to stop when it's taken out. This is how we do same things in IDEA and it works fine for years.

What we have now is that if you do new JProgressBar() but don't actually show it on the screen -- the timer doesn't have a chance to be stopped.

A workaround is to explicitly call "progress.getUI().uninstallUI(progress)".

Please forward this to the people who can fix it.

Kirill

Thanks, Kirill, thank you very, very much!!!!!

You give back hope to all the abandoned and lost people on Mac OS X :-)))

Thanks Kirill. This is the kind of support IDEA users of old are used to.

Please reopen, the issue is still there!

Sorry to say so but the issue is still there in Select #7860 and didn't change at all. CPU load will steadily increase for every compile either under Mac OS X JVM 1.5 or JVM 1.6 (64 bit) on Intel Mac Boo Pro. In current Diana EAP everything seems fine. I would suggest to get this fixed before releasing 7.0.4.

The good message: cpu load is a lot lower now and overall things got better.

The bad message: After quite a few compiles the idle load is steadily increasing. It's not close as bad as before but still there (Around 10% - 12% after quite a lot of compiles). I will attach a cpi and memory snapshot.

(Mac OS X JVM 1.5, All plugins disabled, Selena #7860)

uploaded snapshots (filename starting with 7860 ...)

Same here as Peter. This does not appear to be fixed on the latest Selena build. I have not tried Diana because that version crashes when opening JSP files.