Facets/debugger viable?

After the introduction of facets the interactive debugger has been extremely unstable. New facets pops up from time to time because web.xml files are found here and there. The configuration of contexts also behaves erratically. Besides the debugger is exceedingly slow (250 secs for a startup of a quite simple configuration!). Of course proper documentation would help, descriptions on how to use the buttons are not usefull, a good rundown of the concepts would probably help though.

Maybe the introduction of facets has been premature, complex projects are probably better of using maven anyway.

Unfortunately I do not see any other solutions to this than foregoing interactive debugging.

Pity!

7 comments

Err, don't you mix up two completely different aspects here?

Facet configuration indeed introduced some new bugs.

But why do you think that's related to debugging? After I got the project setup right I have no problems concerning debugging.

0

You are right, those are two different aspects. It is just that (in my case anyway) the bugs appear when i debug, and therefore debugging and facets bugs appear linked to me.

Maybe the bugs would go away if i "got the setup right", i do not think so though. One of the problems is that the debugger slows down to a crawl from time to time. The fix is to clear the project, reload the files and setup the project again. Another bug is that idea insists on scanning all files in the JDK each time focus gets back to Idea (same fix). Does not sound like configuration problems to me, but who knows?

But since you are not experiencing anything of the sort, i guess lies somewhere in the combination of facets/my setup/debugging.

Anyway i guess i will just have to live without debugging for a while.

0

Hello Henrik,


Anyway i guess i will just have to live without debugging for a while.


What about uploading a couple of CPU snapshots demonstrating the problem?

-tt


0

Sure.

What do you mean by CPU snapshots, exactly? Screendumps of KSysGuard? Any other configuration information you will, need? Some java tracing f. ex?

It may take me a while to produce the information since I have just reset my project. But the good thing is when i get the error it is easily reproducable.

Regards
Henrik

0

Hello Henrik,

What do you mean by CPU snapshots, exactly? Screendumps of KSysGuard?
Any other configuration information you will, need? Some java tracing
f. ex?


Based on your description, I assume that two things could be useful:
1) CPU snapshot covering period of long waiting:

Details on how to enable the built-in profiler:
http://support.jetbrains.com/kb/entry.jspa?externalID=192&categoryID=5

2) Stacktrace when IDEA appears not to respond:
http://support.jetbrains.com/kb/entry.jspa?externalID=260&categoryID=4

Create a new JIRA ticket at http://www.jetbrains.net/jira
(Project: "IDEA: Feedback)

Attach the CPU snapshot (and perhaps the stacktrace), and a short description
of your project/activity.
For debugging performance issues, I would expect number of classes in project,
number of/type of breakpoints used, JVM details etc to be of interest.

-tt


0

Ok, i will do that when the problem appears again.

0

Only it has not for some time, maddening!

0

Please sign in to leave a comment.