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 28774 - Getting display name for vcs node accesses disk data from AWT Thread
Summary: Getting display name for vcs node accesses disk data from AWT Thread
Status: RESOLVED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: vcscore (show other bugs)
Version: 3.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Martin Entlicher
URL:
Keywords: PERFORMANCE
: 37679 (view as bug list)
Depends on: 32089
Blocks:
  Show dependency tree
 
Reported: 2002-11-15 10:24 UTC by Peter Zavadsky
Modified: 2005-01-05 19:37 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
AWT stack (2.18 KB, text/plain)
2002-11-15 10:44 UTC, Peter Zavadsky 		Details
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 Peter Zavadsky 2002-11-15 10:24:04 UTC 
I got a couple of seconds freeze and made thread
dump to see what's going on. 
Interested was the stack of AWT thread. There are
accessed data on disk, which should be avoided.
Comment 1 Peter Zavadsky 2002-11-15 10:44:39 UTC 
Created attachment 7955 [details]
AWT stack
Comment 2 Martin Entlicher 2003-02-20 12:21:28 UTC 
It would be hard to solve this and I'm not even sure, that the lazy
loading will improve the performance, because the display name would
have to be refreshed afterwards.
Perhaps we should create some reasonable time limit for the disk
access so that it will not block AWT if the disk access time is long
or something bad happens, and it will not degrade performance when the
disk access is fast.
Comment 3 Martin Entlicher 2003-08-08 11:38:29 UTC 
In order to fix this, the file status caching system would have to
support the lazy loading from disk. The caching system will be
re-designed (issue #32089), making this dependent on it so that this
requirement will be addressed.
Comment 4 Martin Entlicher 2004-01-28 10:53:44 UTC 
*** Issue 37679 has been marked as a duplicate of this issue. ***
Comment 5 Martin Entlicher 2005-01-05 19:37:13 UTC 
Fixed by the new cache implementation.