Inspector Exits Without Completion
Do I need to do something, other than post a comment, to re-open a bug that was closed?
This issue is not fixed and it's a major issue. If we can't figure a way to resolve it without waiting for another EAP, then that will be 3 releases in a row that have been unusable.
http://youtrack.jetbrains.net/issue/WI-4718?projectKey=WI&query=by%3A+me
请先登录再写评论。
Whew, Ok, I think I found the problem. It appears that an Inspector profile that we use won't complete, but the Default will. I'll see if I can modify the Default and if that will work.
Well, no. It works on a limited portion of my project only. Bug exists and is critical.
Message was edited by: Keith Davis
Well, *that* specific exception was fixed and we can't reproduce it anymore.
Please file a new report, with idea.log and inspection profile attached.
Ugh, again, another unusable version? We count on the Inspector now for deployment....:(
Can someone remind of where to get the idea.log?
Sure: http://devnet.jetbrains.net/docs/DOC-1202 (see at the bottom)
Whoa. I just tested something that I thought was happening with the last exception, and confirmed.
I can get it to finish if I don't take the focus away from the IDE. That means, I can't do anything else. The Inspector takes about 2-3 minutes to run (big project.) If I click on any other application, it exits.
I can duplicate this behavior easily.
Created issue and attached log.
http://youtrack.jetbrains.net/issue/WI-4912
Is there any way to get access to nightly builds (or whatever process you run), so that we can maybe assist in this process and not have to wait so long?