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: | Building tooltip calls versioning.Utils.canWrite() | ||
---|---|---|---|
Product: | editor | Reporter: | mklaehn <mklaehn> |
Component: | Painting & Printing | Assignee: | Miloslav Metelka <mmetelka> |
Status: | RESOLVED WORKSFORME | ||
Severity: | blocker | CC: | bsbc99, dlipin, jmichelberger, misterm, mjreged, mklaehn, ovrabec, pcdinh, sreimers, t_h |
Priority: | P4 | Keywords: | PERFORMANCE |
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://statistics.netbeans.org/exceptions/detail.do?id=158522 | ||
Issue Type: | DEFECT | Exception Reporter: | 158522 |
Attachments: |
nps snapshot
nps snapshot |
Description
mklaehn
2009-10-07 13:28:29 UTC
Created attachment 89004 [details]
nps snapshot
AWT is stuck on java.io.File.canWrite(). Versioning has to call this method, is there a chance you don't access FS in AWT? Please evaluate. The first two calls come from org.openide.nodes.FilterNode, the third then from CloneableEditorSupport. Maybe PasteAction state could be updated asynchronously out of AWT Created attachment 91565 [details]
nps snapshot
It has over 100 duplicates already. Can anyone take a look at it? http://statistics.netbeans.org/exceptions/exception.do?id=361926 is about canWrite being slow. http://statistics.netbeans.org/exceptions/exception.do?id=360317 is about canWrite being slow. Seems to me that recent reports that took over 10s lead to versioning. But looking at 360270, the versioning is unlikely to be the cause (as there is just a single query canWrite state). There is another thread with does File.listFiles (but again only once), but that may be the cause of the slowdown. Maybe WinNT system is blocked by that query. Let's use this issue to track: http://statistics.netbeans.org/exceptions/exception.do?id=370387 Building an editor tooltip seems to require disk access! That is unfortunate, the CloneableEditorSupport already knows whether the file is read-only or read write. (In reply to comment #7) > Let's use this issue to track: > http://statistics.netbeans.org/exceptions/exception.do?id=370387 ReadOnlyFilesHighlighting was added in 6.9 and so the above snapshot has nothing to do with the original snapshots. If somebody suggests how to determine the read-only status of an edited file I can change this highlighting layer. This, however, is unlikely to fix the other problems. Bug prior to 7.0, not touched for the last 2 years --> P4. The last report is over one year now. Probably not a problem any more (or?). Closing as works for me. |