Total re-index after crash

Answered

IDE consumes a lot of time after crash (force-quit) - it starts full reindexing of all dependencies of (java) project! That behaviour does not seem reasonable to me at all. If it crashed - it must only restore what was really corrupted, yet it re-indexes ALL, consuming a lot of time and resources. Is there any way to prevent such offensive behaviour?

8 comments
Comment actions Permalink

Hi Denis - we are working on improving the IDE's behavior with regards to indexing in various scenarios.

Could you please reproduce the issue and attach the logs generated with Help | Collect Logs and Diagnostics Data?

1
Comment actions Permalink

One way to test this is under elementaryOS 6, start a lot of memory consuming applications like multiple React frontends served by node servers, Postman, Slack alongside IntelliJ with multiple Spring Boot Servers running from IntelliJ

At some point, elementaryOS will start killing processes. When it kills IntelliJ, then after manually starting IntelliJ again, it starts reindexing the whole project which takes sooo much time

0
Comment actions Permalink

it starts reindexing the whole project which takes sooo much time

To investigate the mentioned issue please collect log files (Help | Collect Logs and Diagnostics Data) and capture CPU snapshot as described here: https://intellij-support.jetbrains.com/hc/en-us/articles/207241235-Reporting-performance-problems#h_dc106c85-2e12-4b67-b530-90deaaa4eb7c

Please upload collected diagnostic data here https://uploads.jetbrains.com/

Or you can create an issue on our issue tracker and attach diagnostic data to the issue: https://youtrack.jetbrains.com/issues/IDEA

Thank you.

0
Comment actions Permalink

I don't see why this would be necessery. The problem here is not that the indexing takes some time, the problem is that I don't see why any indexing is needed at all after a restart. This looks like a conceptual problem with the way IntelliK determines when to index

 

0
Comment actions Permalink

Normally indexing is not triggered on every restart. To find the root cause of this I would need log files.

0
Comment actions Permalink

I can confirm this happens with RubyMine on macOS every time when the IDE is force quit. Doesn't happen if you exit the app the normal way. Uploaded the logs, 2021_12_02_D5sbeshejpARgvV1 is the upload ID. 

0
Comment actions Permalink

Pavel Kachanov Thank you for sharing logs, as I can see your build is: #RM-212.5080.58, 24 Aug 2021. Please try updating to the latest version, this issue was fixed.

0
Comment actions Permalink

Sam Lukashenko Thanks for pointing that out to me, upgraded.

1

Please sign in to leave a comment.