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 27369 - Long freeze whe working with java source
Summary: Long freeze whe working with java source
Status: RESOLVED INVALID
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: -S1S-
Hardware: PC Linux
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2002-09-17 09:54 UTC by Peter Zavadsky
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
full thead dump during the freeze (20.12 KB, text/plain)
2002-09-17 09:56 UTC, Peter Zavadsky
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Zavadsky 2002-09-17 09:54:54 UTC
Build 200209110100, jdk 1.4.1-rc

I was working with java source, and also invoked
Find dialog. It appears a long freeze until the
dialog was shown. Made a thread dump during that
time (see attachment).

One of the caveats seems to be accessing disk from
AWT thread. 
Ofcourse there are also CVS and java parsing
threads which could cause starvation of AWT, but
the accessing disk from AWT should be avoided
anyway, I guess.
Comment 1 Peter Zavadsky 2002-09-17 09:56:00 UTC
Created attachment 7429 [details]
full thead dump during the freeze
Comment 2 Svata Dedic 2003-01-07 12:46:07 UTC
Sorry, but listing contents of java.ext.dirs is not harmful. Since I
saw more slowdowns and pseudo-deadlocks on Linux in filesystem
implementatation, I am quite inclined to blame JDK implementation.
Does that happen with IBM or Blackdown JDKs ?