History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: IDEADEV-12381
Type: Usability Problem Usability Problem
Status: Open Open
Priority: Major Major
Assignee: Maxim Shafirov
Reporter: Vladislav Kaznacheev
Votes: 1
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
IDEA: Development

Provide clear warning and suggest restart when IDEA detects caches corruption

Created: 30 Nov 06 19:25   Updated: 06 Nov 08 23:27
Component/s: User Interface
Fix Version/s: Undefined

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Issue Links:
Duplicate
 
This issue is duplicated by:
IDEA-9332 Window title bar doesn't update name ... Resolved


 Description  « Hide
Many bug reports may be traced down to corrupt caches, and the usual reply (in IDEA Feedback or support) is to delete caches and restart IDEA.

In fact IDEA may save the user's time and inform them about the corrupt caches as soon as it detects this situation.

Suggested functionality:

  • First time this happens after the start, IDEA displays a message saying what happened and suggesting to restart IDEA.
  • If the user accepts, IDEA shuts down.
  • If the user declines (e.g. to finish something he was in the middle of), IDEA does not display the message until IDEA exits.


 All   Comments   Work Log   Change History      Sort Order:
Derek Foster - 16 Jan 07 03:12
It would be nice if Idea would detect which caches are corrupt and offer to rebuild just those caches.

Right now, the only way to force rebuild of caches that I am aware of is to stop Idea, delete all cache files, restart Idea, and wait about 15-20 minutes while it tries to rebuild cache files for the JDK, etc. This is REALLY ANNOYING when it happens in the middle of a critical project. Most of the time is spent rebuilding caches which are not even corrupt, but since there is no way to determine this, they all get rebuilt.

It would also be nice to somehow be able to activate a key combination to clear the cache for a specific source file, and then cause the file to be reparsed, and all error messages, etc. be regenerated from scratch. Idea's error messages sometime get "stuck" on files, and the only way I have found to fix the situation is to insert some garbage at the beginning of the file after the package statement (thus causing Idea to mark the whole file contents as an error) and then delete the garbage again (causing Idea to reparse the file).