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.
Build: NetBeans IDE 7.4 (Build 201310111528) VM: Java HotSpot(TM) 64-Bit Server VM, 24.45-b08, Java(TM) SE Runtime Environment, 1.7.0_45-b18 OS: Mac OS X User Comments: Quasaur: Opening a project. Quasaur: I was changing options in the project properties dialog for com.actionbarsherlock michaelmogessie: I was trying to open An Enterprise application project I have been working on. I can open the EJB module but I get this error when trying to open the war module. Also, after opening another enterprise application, I got this error when trying to open the EJB module but I was able to open the war module without any problems. The problem went away for the other application when I did a 'clean and build' but that is not helping with this one. sdvic: Library problems with Android app GUEST: I don't know what append Stacktrace: java.lang.StackOverflowError at java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:883) at org.netbeans.modules.masterfs.filebasedfs.fileobjects.FileObjectFactory.getCachedOnly(FileObjectFactory.java:685) at org.netbeans.modules.masterfs.filebasedfs.fileobjects.FileObjectFactory.getCachedOnly(FileObjectFactory.java:671) at org.netbeans.modules.masterfs.filebasedfs.fileobjects.FileObjectFactory.issueIfExist(FileObjectFactory.java:290) at org.netbeans.modules.masterfs.filebasedfs.fileobjects.FileObjectFactory.getFileObject(FileObjectFactory.java:226) at org.netbeans.modules.masterfs.filebasedfs.fileobjects.FileObjectFactory.getValidFileObject(FileObjectFactory.java:788)
Created attachment 145689 [details] stacktrace
Probably a problem in NBAndroid plugin. Method o.n.m.android.project.queries.ClassPathProviderImpl.fillLibraryProjects seems to be called in an infinite recursion. Reassigning to Radim Kubacki. Please evaluate it. Thank you.
Thanks, I'll take a look and need to make the code more robust. BTW: why is it not possible to see messages.log files from exception reports?
Will be fixed in 1.235 - https://bitbucket.org/nbandroid/nbandroid/commits/99ff8d86bf28ecd55c1660d5efbce72c93e3c5c8
*** Bug 252753 has been marked as a duplicate of this bug. ***