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 18438 - File reload takes very long time
Summary: File reload takes very long time
Status: CLOSED DUPLICATE of bug 11692
Alias: None
Product: editor
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: Sun Solaris
: P3 blocker (vote)
Assignee: issues@editor
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2001-12-07 04:51 UTC by _ jrichard
Modified: 2007-11-05 13:44 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
stack trace from deadlock (10.34 KB, text/plain)
2001-12-07 04:59 UTC, _ jrichard
Details
More thread dumps. (34.04 KB, text/plain)
2001-12-07 08:43 UTC, Jan Lahoda
Details

Note You need to log in before you can comment on or make changes to this bug.
Description _ jrichard 2001-12-07 04:51:42 UTC
NetBeans 3.3RC1, JDK 1.3.1, Solaris 2.6

I was viewing a file in the NetBeans editor when I realized
I needed to change it.  To do so, I copied another file into
the same name as the original file (ie, edit file.txt, 
cp /home/jrichard/file.txt file.txt).  After doing this
netbeans apparently tried to use the new file, but deadlocked
while doing so.

This normally works and I haven't seen this error before, but this
time I grabbed a copy of the stack trace.  My uneducated guess
is that "OpenIDE Request Processor-0" is doing something that should
be done on the AWT event queue thread.  I'll attach the stack trace.

In any case, I had to kill the ide and restart.
Comment 1 _ jrichard 2001-12-07 04:59:10 UTC
Created attachment 3728 [details]
stack trace from deadlock
Comment 2 Jan Lahoda 2001-12-07 08:40:18 UTC
Hi,
   I saw this before. This is not a deadlock, the IDE will be unfrozen
after long time (in some case 1-2 minutes, maybe even more?).
I will attach my thread dumps, it can be clearer from them where the
time is spent.
I am leaving this as P3, because it probably is not a deadlock.
Changing summary, please change back if you disagree.
Comment 3 Jan Lahoda 2001-12-07 08:43:21 UTC
Created attachment 3729 [details]
More thread dumps.
Comment 4 Petr Nejedly 2001-12-10 13:20:32 UTC
Hmm, big document?
Doesn't it bear on the implementation of DocMarks?
see #11692, I think we could mark this as a duplicate,
even when the code paths are a bit different.
Mila is working on changes in DocMarks, I hope
it will cover this issue as well.

*** This issue has been marked as a duplicate of 11692 ***
Comment 5 Jan Lahoda 2001-12-10 13:25:57 UTC
Only to say it all, the file does not have to be big (if you do not
think 25kB is big). It does not happen so visibly each time, sometimes
it is quite fast, but once it become slow, it takes commonly 20
second, and I saw cases for approximately 1-2 minutes (as I mentioned
above).
Comment 6 Quality Engineering 2003-06-30 18:01:35 UTC
Resolved for 3.3.x or earlier, no new info since then -> closing.
Comment 7 Quality Engineering 2003-06-30 18:08:29 UTC
Resolved for 3.3.x or earlier, no new info since then -> closing.