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 62138 - IDE hangs up when expanding a folder in Versions panel containing some 50-plus subfolders.
Summary: IDE hangs up when expanding a folder in Versions panel containing some 50-plu...
Status: RESOLVED WORKSFORME
Alias: None
Product: obsolete
Classification: Unclassified
Component: vcscore (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P1 blocker (vote)
Assignee: issues@obsolete
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2005-08-10 21:20 UTC by ayermolayev
Modified: 2005-09-05 15:40 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Full JVM thread dump (13.97 KB, text/plain)
2005-08-18 21:48 UTC, ayermolayev
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ayermolayev 2005-08-10 21:20:24 UTC
The problem appears when I try to expand a folder in the Versions tree panel 
which contains just 54 subfolders and no files.
Comment 1 Martin Entlicher 2005-08-11 12:00:37 UTC
Can you please attach a thread dump?
The folders are checked for sharability, which triggers the projects system. Are
there many projects between these 50+ folders?
Comment 2 ayermolayev 2005-08-18 21:48:56 UTC
Created attachment 24063 [details]
Full JVM thread dump
Comment 3 ayermolayev 2005-08-18 22:02:25 UTC
The problem does not appear every time -- usually it happens during an 
intensive browsing in the CVS tree. So you never know whether your next 
attempt to expand a version node will succeed or it will hang up the IDE, and 
next time it could be a different node.
The troublesome node type can be any -- a folder, a file, a branch.
Comment 4 Martin Entlicher 2005-09-05 15:40:44 UTC
This is not a hang (according to the thread dump) - the IDE sems to be just
bussy with getting the children, and it should consume CPU. There is nothing
from VCS. It's strange that all calls end in HashMap.get() - but this can be a
just a coincidence.

Resolving as works for me - I was not able to reproduce this.
If this still happens in some configuration, please make several thread dumps -
so that we can see how this evolves in time and also check the CPU activity. Thanks.