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: | [50cat] NB Freezes after update center and tools options selection | ||
---|---|---|---|
Product: | editor | Reporter: | claudio4j <claudio4j> |
Component: | Options | Assignee: | issues@editor <issues> |
Status: | RESOLVED WORKSFORME | ||
Severity: | blocker | CC: | jchalupa, mroskanin |
Priority: | P3 | Keywords: | THREAD |
Version: | 5.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
screenshot 1
screenshot 2 |
Description
claudio4j
2005-09-29 14:23:50 UTC
Created attachment 25302 [details]
screenshot 1
Created attachment 25303 [details]
screenshot 2
I tried to see the thread dump: kill -3 PID, no results... I killed the process, kill PID Started again, go to Tools --> Options, them "Negative value is not allowd" (ok, known bug), the exit, options, go to Tools --> Options again, everything now shows to be fine (code template and macros) Then I removed netbeans install and user dir (rm -rf ~/.netbeans ~/javaSoftware/netbeans*) Installed NB again and started, updated modules, when modules installment ends, exit netbeans. started NB again, go to tools --> options, it shows "negative value is not allowed" (known bug, ok), then Editor option --> "macro" and "code template" shows the 1st screenshot, drop down list, shows no values, go to cancel button, then got back to tools --> Options , everythin shows fine now. To let you know, the selected modules Derby CVS Profile JMX and marked all of them "Global" and "Yes to all" Known editor/options issue? The bug I refer, when I wrote "go to tools --> options, it shows "negative value is not allowed" (known bug, ok)" http://www.netbeans.org/issues/show_bug.cgi?id=64597 I will look at it. Too late to fix in nb5.0. I am sorry, but I could not reproduce this. I installed some global modules from AU, restarted Netbeans and Tools-Options showed up nicely after that. Without the full thread dump the chances for catching this deadlock are pretty low. |