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.
When I attempt to launch a version of NetBeans that I built from the tip of the main-silver repository, it crashes the JAWS screen reader (version 13.0.1006), under Windows 7 Ultimate 64-bit. I compiled NetBeans using JDK 7 (via the -Dpermit.jdk7.builds option passed to ant on the command line), and am using Java 7 as the JRE. Steps to Reproduce: 1) Build NetBeans using JDK 7.x on Windows, with the following command line: <Shell> ant -Dpermit.jdk7.builds=true 2) Once the build finishes, navigate to ${NetBeans_source}\nbuild\netbeans\bin. 3) Launch either NetBeans.exe or NetBeans64.exe with JAWS 13 running. When the main screen comes up, all speech will be lost, and the system will start behaving erratically, necessitating a forced shutdown of JAWS (using the keystroke Insert+Windows+F4).
Please confirm if the problem appears also with the official daily build available at http://bits.netbeans.org/download/trunk/nightly/latest/
(In reply to comment #1) > Please confirm if the problem appears also with the official daily build > available at > http://bits.netbeans.org/download/trunk/nightly/latest/ The screen reader no longer seems to crash, however, Windows sees the program as "not responding." Tab and Shift+Tab do not work to move through controls. Does this perhaps have anything to do with the fact that I am using JDK/JRE 7 for the IDE?
I just attempted another test, this time launching NetBeans (the nightly build) from the command line, and I get console output that seems to point to a java.lang.NullPointerException in the Java Access Bridge. However, this output doesn't seem to point to any specific place in the NetBeans codebase from which the exception could have propagated up the call stack. I can't seem to replicate this behavior all the time--it appears to be an intermittent fault, no matter what way I try to invoke the IDE--netbeans.exe or netbeans64.exe.
Unfortunately we don't have your screenreader to try reproducing. Can you please report the problem to the producer of JAWS with as many details as possible (OS and Java version, the complete exception stacktrace, etc.)? Trying it with some other Java apps (at least SwingSet demo running with the same version of Java) might be a good idea as well. Searching for articles about unresponsiveness related to the reader has shown various older mentions of unresponsiveness problems that they were fixing on their side.