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.

Bug 251053 - File cache causing errors
Summary: File cache causing errors
Status: RESOLVED INCOMPLETE
Alias: None
Product: editor
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 8.0.2
Hardware: PC Linux
: P2 normal (vote)
Assignee: Milutin Kristofic
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-10 07:17 UTC by szpraai
Modified: 2015-03-11 06:05 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description szpraai 2015-03-10 07:17:08 UTC 
I'm using Ubuntu 14.04 with NetBeans IDE 8.0.2 (Build 201411181905). After editing multiple files (like a hundred), sometimes the file cache(?) becomes glitchy, and when I try to build the project, it says e.g.: "; missing at line ...", but when I open that file in the editor, that line doesn't even exist. Then I go to /home/.../.netbeans/8.0.2/var/filehistory, delete everything, and it just builds without the previous error. It's really annoying that I have to do this manually at least 10 times a week. Could there be an option as a workaround that Netbeans would delete cache on exit, or a button to "Clear cache" or something? It would be appreciated.
Comment 1 Milutin Kristofic 2015-03-10 17:04:19 UTC 
FileHistory is not cache. Folder cache/index is cache of files. Are you sure that deleting just FileHistory solve the problem? 

Can you please attach messages.log? You are probably writing java code. Can you write more details, so I can reproduce this bug. Are you using normal disk, or network disk? Any ideas what is causing problem are welcome. Thank you.
Comment 2 szpraai 2015-03-11 06:05:24 UTC 
Sorry, my mistake. I am 100% sure that deleting FileHistory solves the problem.

Yes, I'm writing Java code, and I'm using a normal (SSD) disk. I don't really know how to reproduce the bug, since it looks "random", but whenever I'll be able to catch it I'll get back to you with the logs! I know it must be really hard to debug without enough info, I will try to gather data.