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.
Summary: | Deadlock in NbJavaCvsFileSystem$JavaCvsAttributes | ||
---|---|---|---|
Product: | versioncontrol | Reporter: | Vitezslav Stejskal <vstejskal> |
Component: | CVS | Assignee: | issues@versioncontrol <issues> |
Status: | VERIFIED WONTFIX | ||
Severity: | blocker | Keywords: | RANDOM, THREAD |
Priority: | P2 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
full thread dump
FTD with DEADLOCK when doing copy&paste action on JavaCVS FS |
Description
Vitezslav Stejskal
2003-02-19 11:16:29 UTC
Created attachment 9019 [details]
full thread dump
Deadlock needs to be fixed into 3.5 Scheduled for next release, will be solved while refactoring settings. isn't it possible easy reproduce by copy & paste actions on JavaCVS FS? I'll check it tomorrow. Increasing the priority to P2 (Deadlock has to be always P2) If this is not much reproducible and does not occur during common tasks I would like to defer this for NB 4.0. The reason is, that this problem will disappear by itself by removing javacvs filesystem from the IDE distribution. Only vcsgeneric (with added profile for cvslib) will be present in NB 4.0. Read the 'Bug Priority Guidelines': P1 - reproducible, unavoidable crash or deadlock P2 - intermittent crash or deadlock, happens fairly often This happens occasionaly during the projects switch, I never saw it when working with regular files. IMO it's not P2. Created attachment 10222 [details]
FTD with DEADLOCK when doing copy&paste action on JavaCVS FS
well, there's only one thing which is common for your scenario and mine scenarion. And it is the thread dump and wisible stacktrace. Also even I'm not able to reproduce everytime my scenario. But it occures when: ==================== Using Nevada RC2, jdk1.4.2 rc #b21, rh80. Mount JAvaCVS FS. HAve already commited some dir structure + files in it. Create a new dir. Copy & Paste in it some already commited subpackages+files. Then the DEADLOCK with almost identical threadDump occures. So, then, I'm still for it is P2 ('cause DEADLOCK are serious) and it is not only about projects, but because it is not 100%reproductable I'm for "solving" it in 4.0. Also the P2 "says" it won't go into 3.5 release/Nevada, right? As described at http://www.netbeans.org/servlets/ReadMsg?msgId=655179&listName=nbusers the development of javacvs module has been stopped. Verified. |