Dialog takes 20 seconds to come up when doing a ctrl-o

This is not a new problem, but something I had with IntelliJ forever: when I do a ctrl-o, the dialog takes something like 20 seconds to come up. Has anyone already seen something like this? And of course, a solution would be more than welcome :).

Alex

18 comments

Could you please send us the CPU snapshot?
To make a snapshot, you may press 'capture CPU data' button at the toolbar,
press Ctrl-O and press the button again after the dialog comes up.

--
regards,
--
Alexey Kudravtsev
Software Developer
JetBrains, Inc, http://www.jetbrains.com
"Develop with pleasure!"

"Alessandro Vernet" <avernet@scdi.org> wrote in message
news:172491.1161139854672.JavaMail.itn@is.intellij.net...

This is not a new problem, but something I had with IntelliJ forever: when
I do a ctrl-o, the dialog takes something like 20 seconds to come up. Has
anyone already seen something like this? And of course, a solution would
be more than welcome :).

>

Alex



0

Also some details on what is the size of the class hierarchy you are working with (i.e. the number of methods in a class and all its super classes/interfaces) would help us a lot.

0

Hi Alexey,

I did what you are suggesting a while ago, and I got an answer from Dmitry saying that the time is spent in Swing code. This was in July 2006 with build 5380, and back then the dialog took 2-3s to come up. I just did a ctrl-o now with build 5784, and it took 28 seconds, which is a little... hem... irritating ;).

Here is the link to the corresponding JIRA issue:
http://www.jetbrains.net/jira/browse/IDEA-8209

Just let me know if you think that I should open a new issue and attach a new CPU snapshot.

Alex

0

Hi Eugene,

How can I know the size of the class hierarchy?

Alex

0

Alessandro,
That snapshot you've attached back then contains just JFileChooser related
stuff.
I presume you was doing File|Open, not Ctrl-O at the moment.
Could you please create the new snapshot during Ctrl-O specifically?

--
regards,
--
Alexey Kudravtsev
Software Developer
JetBrains, Inc, http://www.jetbrains.com
"Develop with pleasure!"

"Alessandro Vernet" <avernet@scdi.org> wrote in message
news:9208951.1161193081849.JavaMail.itn@is.intellij.net...

Hi Alexey,

>

I did what you are suggesting a while ago, and I got an answer from Dmitry
saying that the time is spent in Swing code. This was in July 2006 with
build 5380, and back then the dialog took 2-3s to come up. I just did a
ctrl-o now with build 5784, and it took 28 seconds, which is a little...
hem... irritating ;).

>

Here is the link to the corresponding JIRA issue:
http://www.jetbrains.net/jira/browse/IDEA-8209

>

Just let me know if you think that I should open a new issue and attach a
new CPU snapshot.

>

Alex



0

Are you trying to override a method (default binding of ctrl-o) or open
a new file?
R

0

Alexey,

As Robert noted, it looks like we are talking about different things. Sorry for the confusion: ctrl-o is mapped to "File / Open File" on my machine.

Is it still worth for me to capture the CPU data and post it somewhere, or should I just wait 20-30s when I want to open an external file, and learn to be patient? ;)

Alex

0

Alessandro, does it still happen with 6.0.1?
Also do the pauses on frame acitvation you talk about at your blog http://www.orbeon.com/blog/2006/10/19/hack-intellij-xml-editor-memory-tuning/
still remain in 6.0.1? The reason I ask is because I've been fixing those kind of problems, but the former fix appeared only in 6.0.1 minor release.

0

Eugene,

Yes. In fact, I figured this out while using 6.0.1. IntelliJ does some work on frame activation. I suspect that with the default settings for -Xms/-Xmx, the portion of the heap that is used by live object gets too close to the total heap size. So on frame activation the VM spends most of its time doing full GCs. Bumping up the heap size takes care of this.

And bumping up the heap size improves performance drastically for me more than just for frame activation. This was just the focus of the blog post because that was the thing that annoyed me the most :).

Alex

0

Eugene,

And I should add that:

1) "File / Open File" does take 20-30 seconds on 6.0.1 (#5784).
2) It still takes the same time after changing the heap size (changing the heap size does not seem to have an impact on the time it takes for the "Open File" dialog to come up).

Alex

0

It looks like there are no follow-up messages on this one. Nobody else mentioned this issue in the past? Would there just be something weird in my environment?

Alex

0

Alessandro,
We are unable to reproduce it here. The only way I see we could figure it out is for you to take a CPU snapshot and post a link here.

0

Eugene,

There is already a snapshot attached to the this JIRA issue:
http://www.jetbrains.net/jira/browse/IDEA-8209

But if all the time is spend in the JFileChooser code, then I guess there is nothing you can see from that snapshot. Right?

Alex

0

Hi,

Do you have network drive mappings?
Something similar was happening to me. It was taking around a minute to
change a directory. But if I disconnect all network drives everything
was working fine.

-serg

It looks like there are no follow-up messages on this one. Nobody else mentioned this issue in the past? Would there just be something weird in my environment?

Alex

0

Sergiy,

No, no network drive mapping.

H:\>net use
New connections will be remembered.
There are no entries in the list.

However it happens that my hard drive is in H:, not C: as usual. There is nothing in all the drives before H:, as those drives are mapped to a multi-card reader (Compact Flash, etc). The BIOS assigns those first letters to the multi-card reader, and then the first next letter to the hard drive.

Of course, there is nothing in any of those drives, so this should not have any impact whatsoever, but this is the only unusual thing I can think of.

Alex

0

The time is indeed spent in JFileChooser. Does it help if you run IDEA under JDK6? I know they've fixed a number of issues with JFileChooser in 6.0.

0

Eugene,

I will give a try to your suggestion next week and let you know.

Alex

0

I finally got to test this with J2SE 6. Now the dialog takes 3 seconds to come up. That seems much better, but still too long, and the improvement might also be due to some other change in my environment rather to J2SE 6.

0

Please sign in to leave a comment.