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.
I have added several Ant tasks to the default build script of my project. One of them simply calls PMD to generate a report. Once the task is completed, the whole IDE freezes and I have no choice but to kill the IDE process. Calling the Ant task from the command line works ok. I had the same problem with NetBeans 5.5.1, but my workaround was to have 2 Ant tasks, the first one was calling the other one using 'antcall'. This workaround doesn't work anymore. Here is the stack trace I got in NetBeans log file in 5.5.1. Unfortunately, there is nothing the the log of NB6 that can help track the problem, so I'm assuming this stack trace from 5.5.1 shows the problem in 6.0 as well, but it could be a different problem (but somehow I don't think so). java.lang.NullPointerException at org.apache.tools.ant.Project.fireMessageLoggedEvent(Project.java:2006) at org.apache.tools.ant.Project.fireMessageLogged(Project.java:2058) at org.apache.tools.ant.Project.log(Project.java:367) at org.apache.tools.ant.Task.log(Task.java:346) at net.sourceforge.pmd.util.AntLogHandler.publish(AntLogHandler.java:45) at java.util.logging.Logger.log(Logger.java:472) at java.util.logging.Logger.doLog(Logger.java:494) at java.util.logging.Logger.log(Logger.java:538) at java.awt.Component.dispatchEventImpl(Component.java:4253) at java.awt.Container.dispatchEventImpl(Container.java:2116) at java.awt.Component.dispatchEvent(Component.java:4240) at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4322) at java.awt.LightweightDispatcher.trackMouseEnterExit(Container.java:4103) at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3968) at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3916) at java.awt.Container.dispatchEventImpl(Container.java:2102) at java.awt.Window.dispatchEventImpl(Window.java:2429) at java.awt.Component.dispatchEvent(Component.java:4240) at java.awt.EventQueue.dispatchEvent(EventQueue.java:599) [catch] at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160) at java.awt.EventDispatchThread.run(EventDispatchThread.java:121) Maybe I'm not calling PMD properly, but still I think NetBeans should be able to recover from whatever error happens when running Ant. I will attach a sample project (a simple Hello world main class) with my custom build.xml. The zip file also includes PMD (I've tried with 4.0 and 4.1), so it should be simple to reproduce on your end. I simply love NetBeans, I hope this report can make it a little better. Francis
Created attachment 54772 [details] The zipped project minus the PMD jar file
Because of the 1 meg size limit for the attachement, I was forced to delete the pmd-4.1.jar from the lib/PMD/lib directory. To reproduce the problem, you will have to get PMD from the project's site. Sorry!
Something to do with PMD registering a custom global LogHandler, which a very dangerous thing for an Ant task to do. Deadlock may not be easily fixable on the NB side, and anyway you would still have huge memory leaks.
Created attachment 54776 [details] Deadlock section of thread dump
I filed a bug for PMD on your behalf; see the URL and add yourself to CC.
Thanks Jesse, that was a very impressive response time! Happy new year, long live NetBeans ;-) Francis