[REF:IDEADEV-35946 ] Code Analysis for single class taking long time(4+ hours and counting).

I wanted to test IDEADEV-35946 that was fixed in the last EAP, to verify that no Stack overflow was encountered.
Performing an 'analize' for all conditions for a single class file,
has been running for over an hour and shows about 50% of CPU usage.
This class file is a simple JUnit, the same as in the JIRA.

According to the Status bar it has been working on a 'backwards Analysis' for about 4.5 hours.

I wouldn't think the analysis would be that deep, considering the class tests a single java class that only depends on the JDK.
If this analysis always takes this long then its just unusable.


Please sign in to leave a comment.