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.
Created attachment 105113 [details] log of the crash The nightly listed below crashes everytime I start. installer: netbeans-trunk-nightly-201101180000-ml-linux.sh Product Version: NetBeans IDE Dev (Build nbms-and-javadoc-5919-on-101012) (#acc8349e2a5b) Java: 1.6.0_18; Java HotSpot(TM) 64-Bit Server VM 16.0-b13 System: Linux version 2.6.35.10-74.fc14.x86_64 running on amd64 Runtime = Java(TM) SE Runtime Environment 1.6.0_18-b07 Java Home = /usr/java/jdk1.6.0_18/jre System Locale; Encoding = en_US (nb); UTF-8 However the previous build works fine: installer: netbeans-trunk-nightly-201101040001-ml-linux.sh Product Version: NetBeans IDE Dev (Build nbms-and-javadoc-5919-on-101012) Java: 1.6.0_18; Java HotSpot(TM) 64-Bit Server VM 16.0-b13 System: Linux version 2.6.35.10-74.fc14.x86_64 running on amd64; UTF-8; en_US (nb) Userdir: /home/toddb/.netbeans/dev
No core file nor hs_error* file was produced.
After removing ~/.netbeans/dev and starting the ide, it works. Then after copying back some of the components of the old director (~/.netbeans/dev.save) it still worked. Specifically cd ~/.netbeans/dev.save tar cf - config/Keymaps/ \ config/Preferences \ config/Preferences.properties \ etc/netbeans.conf \ | (cd ../dev; tar xvf -) However, after I copied back ~/.netbeans/core/org-openide-filesystems.jar it began dying at start up again. Removing that one file made it work again. Finally, restoring the entire old ~/.netbeans/dev and removing the file above caused it to work fine.
I guess you have identified the problem. It is the ~/.netbeans/core/org-openide-filesystems.jar. What else can we do for you? Maybe you can attach the file here and we can check whether it is corrupted or OK...
Created attachment 105568 [details] jar file that caused the crash.
The file is really corrupted. Trying: $ unzip -v the-file.jar fails miserably. The question is how the file got to your computer and how it got corrupted (during install or later?). I am not however sure I want to know all the details. Passing to platform to potentially print some useful message into the log.
A better question might be: can you recognize a corrupt jar file and set it aside before it crashes the system.