30-40 second pauses in debugger, 'Collecting data...'

Avatar
Permanently deleted user
Created

Hi, all.

I've been looking through this newsgroup, but haven't found anything
recently that looks to address this problem.

I've been using Irida for about 2 weeks (previously I was using 4.5). I'm
currently running build 3386 of Irida, and before that had build 3378. In
both builds, there are significant pauses when a breakpoint is reached, with
the display simply saying 'Collecting data...'. My timing (objective) is
that these take 30-40 seconds to complete. (Subjectively it takes much,
much longer :).

As an attempt to describe my environment, I'm on a Windows XP platform, SP 2
on a 3.2 Ghz Xeon processor, with 3GB memory. I have JDK 1.5.0_04. running
Remote Debugging using Socket transport, attaching to a 'client' and a
'server' process both running on my machine. The 'client' is running a unit
test, so not very heavy. The 'server' is running under JBoss. When the
debugger is waiting on the 'Collecting data...', my Cpu is basically idle,
and memory usage isn't high or climbing.

Debugging the same project under Idea 4.5 (except using JDK 1.4.2_08)
displayed no such delays.

Anyone got any ideas? Is there anything else in my setup that could help
diagnose what's wrong? I wanted to post here in case this is a known issue,
before logging it.

Thanks!

Bob.


Votes

0

Share

34 comments
Avatar
Permanently deleted user
Created

M. J. Milicevic wrote:

running 3417 right now, and haven't seen "collecting data" yet ;)


Excellent - I havn't got to debugging yet, IDEA is hanging on find
usages quite often now :( no exceptions. time for a thread dump I think.


0
Avatar
Permanently deleted user
Created

running 3417 right now, and haven't seen "collecting data" yet ;)

Fine.

Does it work better in your environment, Bob?

--
Best regards,
Eugene Zhuravlev
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"


0
Avatar
Permanently deleted user
Created

Excellent - did this fix make it into #3417 or the next build?


Yes, it must be there.

--
Best regards,
Eugene Zhuravlev
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"


0
Avatar
Permanently deleted user
Created

Just downloaded build 3417 - looks like you did indeed track down and fix
the problem. Thanks for continuing to chase this over the past 2+ weeks!

That certainly drops the importance to me of IDEA-3614!

Bob.

"Eugene Zhuravlev (JetBrains)" <jeka@intellij.com> wrote in message
news:dbl3fr$11b$1@is.intellij.net...

Hello Bob,

>

Seems like finally I have found the reason thanks to your very detailed
descriptions. It is indeed a threading issue. More specifically: the more
threads are running in your application and the larger stacks they have,
the more slow was debugger rendering stack data - just because of one JDI
call that turned out to be quite expensive. This is especially noticible
when debugging application servers with lots of threads running,. Now the
debugger works much snappier.
I wish every our customer provided such detailed feedback like you did,
thanks a lot for this and I hope you'll enjoy faster debugger!

>

--
Best regards,
Eugene Zhuravlev
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"



0

Please sign in to leave a comment.