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.
1.6.0-rc-b71, Slackware 10.2 (probably does not matter) I have e.g. openeded apisupport/project -> package org.netbeans.modules.apisupport.project.ui.customizer. Hold key-down and IDE is frozen, 100% CPU is eaten and you have to wait, sometime few, cca 1-7, second on my machines (D505). In 5.0 the same is quite fast.
Radime it is due to that the PMD autoscanning feature is on. Sorry I have it still turned on :) Probably performance team does not care too much about this case, removing. I'll attach a thread dump for you.
Created attachment 28915 [details] pmdInAction.txt
This is a code I inherited and never actualy used too much. I need to rewrite the parsing queue. Probably to use RP rather than own tread and post the jobs here.
> I need to rewrite the parsing queue. Probably to use RP rather than own tread > and post the jobs here. I do not understand why and what you want to do/fix but I thought that the fix should be that you do not start PMD at all when the active top component is not editor - we talk about auto-scanning (Enable Scan = true in Options). Why would you want to scan a java file under selected node in the explorer when the result of pmd-scanning action will not appear anywhere (neither in OW neither in Editor TC). I suppose, just do not run the PMD action in those cases. When: - (autoScanning == true && activeTC != editor) --> do not run PMD action, since it does not make any sense. Only when user invokes PMD explicitely (shortcut or Tools | Run PMD) run PMD action in all cases no matter what activeTC is. Should be probably easy fix. And also important, since due to this bug I was forced to switch this nice autoScanning options off.
fixed in pmd1.5.1 that's already released.