This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | java.io.IOException: Cannot delete: C:\Users\Tjeerd.SIVZ\AppData\Local\NetBeans\Cache\7.3\index\s65\java\14\refs\nb-lock-write.lock(true,true,true,true,true,null,{Thread[State Data Manager,5,IDE Main] | ||
---|---|---|---|
Product: | editor | Reporter: | Exceptions Reporter <exceptions_reporter> |
Component: | Parsing & Indexing | Assignee: | Tomas Zezula <tzezula> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | pbradley, sdedic |
Priority: | P3 | ||
Version: | 7.3 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | 199911 |
Bug Depends on: | 228041 | ||
Bug Blocks: | |||
Attachments: | stacktrace |
Description
Exceptions Reporter
2013-03-26 14:30:57 UTC
Created attachment 133087 [details]
stacktrace
Caused by Groovy support which I've (un)fortunately rescued. The thing is that groovy invalidates java indexer and breaks its invariants. This can probably be closed. The problem was that killing Netbeans did not actually stop the process so when I restarted, the old process was still hanging around locking the cache folder. I exited from Netbeans then killed the original process. All seems to be fine now. (In reply to comment #3) > This can probably be closed. The problem was that killing Netbeans did not > actually stop the process so when I restarted, the old process was still > hanging around locking the cache folder. I exited from Netbeans then killed the > original process. All seems to be fine now. Closing, backgrounded instance of NetBeans probably held the lock file open - was not possible to delete it on Windows. Thanks for the notice. |