
|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
Windows XP SP2, Core 2 Duo, 2GB memory.
|
|
| Build: |
7,757
|
| Severity: |
High
|
I am unable to use Inspect code from the Analyze menu, because it never finishes performing backward analysis.
If I just perform backward dependency analysis with the default settings, it never finishes either. Instead, it seems to scan the whole module root including all the library sources and javadocs. This will eat up all the available memory until IDEA freezes. I have tried to give IDEA over 1 GB of memory, but the same thing happens. As I workaround I can specify a very narrow scope of interest, including files only from the src-folder. The scope of interest is unfortunately not available in Inspect code, so it will always try to scan the whole content root for backward dependencies. Because of this, I have not been able to succesfully run Inspect code ever with IDEA 7.
With IDEA 5.x I don't remember having this problem.
|
|
Description
|
I am unable to use Inspect code from the Analyze menu, because it never finishes performing backward analysis.
If I just perform backward dependency analysis with the default settings, it never finishes either. Instead, it seems to scan the whole module root including all the library sources and javadocs. This will eat up all the available memory until IDEA freezes. I have tried to give IDEA over 1 GB of memory, but the same thing happens. As I workaround I can specify a very narrow scope of interest, including files only from the src-folder. The scope of interest is unfortunately not available in Inspect code, so it will always try to scan the whole content root for backward dependencies. Because of this, I have not been able to succesfully run Inspect code ever with IDEA 7.
With IDEA 5.x I don't remember having this problem. |
Show » |
| There are no comments yet on this issue.
|
|