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 57341

Summary: VCS: IDE hangs when trying to edit a checked in form
Product: editor Reporter: Andrei Chistiakov <ca-nb>
Component: -- Other --Assignee: issues@editor <issues>
Status: RESOLVED DUPLICATE    
Severity: blocker    
Priority: P2    
Version: 4.x   
Hardware: PC   
OS: Windows ME/2000   
Issue Type: DEFECT Exception Reporter:
Attachments: One thread dump.
Another thread dump.

Description Andrei Chistiakov 2005-04-01 15:13:46 UTC 
Build 200503301800

When a project is under version control, a local copy of a checked in form is
read-only. Opening the read-only form in editor and attempt to modify it, for
instance, by putting a new GUI control on it hangs IDE.
Comment 1 Andrei Chistiakov 2005-04-01 15:25:22 UTC 
Reproduced with MS Visual Source safe.

Workaround: check out the form prior to editing.
Comment 2 Jan Stola 2005-04-01 15:53:59 UTC 
I am not able to reproduce this with read-only files not under version control
and with read-only files in CVS. So, it seems to be MS Visual Source safe
specific issue. Reassigning to vcscore module for evaluation.
Comment 3 Martin Entlicher 2005-04-02 18:44:52 UTC 
The thread dump is necessary to evaluate this.
I'll attach the thread dump if I'll be able to reproduce it on Windows.
Comment 4 Martin Entlicher 2005-04-02 19:33:34 UTC 
Next time, please attach the thread dump. It would speed up the evaluation process.
Comment 5 Martin Entlicher 2005-04-02 19:34:21 UTC 
Created attachment 21311 [details]
One thread dump.
Comment 6 Martin Entlicher 2005-04-02 19:34:52 UTC 
Created attachment 21312 [details]
Another thread dump.
Comment 7 Martin Entlicher 2005-04-02 19:36:04 UTC 
This is not a deadlock, but AWT consumes 100% CPU.
This is similar to one issue, which I have already passed to editor module. This
might be a duplicate.
Comment 8 Miloslav Metelka 2005-04-04 09:47:22 UTC 
This is dup of issue 57104 which was fixed recently (on last Friday evening).
Thanks for the report.

*** This issue has been marked as a duplicate of 57104 ***