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.
Hello NetBeans is dying on me when I open a 1.5 MByte java source file. NetBeans freezes and displays no error but the log file records the following: SEVERE [org.openide.util.RequestProcessor] java.lang.NullPointerException at org.openide.text.CloneableEditor$DoInitialize.run(CloneableEditor.java:261) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:561) [catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:986) You may well ask what am I doing with such a big source file, well it was auto generated by axis2's wsdl2java and I have no desire to re-write it. Any idea what is causing the crash or how to cure it ? I am using: Product Version = NetBeans IDE 6.1 (Build 200805300101) Operating System = Windows XP version 5.1 running on x86 Java; VM; Vendor = 1.5.0_12; Java HotSpot(TM) Client VM 1.5.0_12-b04; Sun Microsystems Inc. Runtime = Java(TM) 2 Runtime Environment, Standard Edition 1.5.0_12-b04 Java Home = C:\Program Files\Java\jdk1.5.0_12\jre System Locale; Encoding = en_GB (nb); Cp1252 I have thought of upgrading the JDK to 1.6 but our application servers are all running 1.5 so I would rather stick with that. Your thoughts would be very much appreciated. Vince
I'd recommend trying this in Nb6.5. There have been lots of bugfixes in this area and chances are that this will just work fine in 6.5. If you can't or don't want to use 6.5 before its final release you can try to set the following property in your <nb-inst-folder>/etc/netbeans.conf. The property is -J-Dorg.openide.text.CloneableEditor.oldInitialize=true and it will turn off performance optimizations for opening files in the editor.
Please try NB 6.5 (latest daily dev build should be fine as we are close to release so it should be stable enough). There was many fixes in openide.text module especially loading documents. Could you generate thread dump and atach it here so that I can find out original bug report?
Also you can install patch for NB 6.1 as it should contain fix for this issue. *** This issue has been marked as a duplicate of 132386 ***
I found original issue so no need to create/attach thread dump.