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 Dev (Build 201408180001) VM: Java HotSpot(TM) 64-Bit Server VM, 25.11-b03, Java(TM) SE Runtime Environment, 1.8.0_11-b12 OS: Mac OS X User Comments: athompson: trying to create html5 project (no template, no js libs) Stacktrace: java.lang.StackOverflowError at java.io.UnixFileSystem.getBooleanAttributes0(UnixFileSystem.java:0) at java.io.UnixFileSystem.getBooleanAttributes(UnixFileSystem.java:242) at java.io.File.exists(File.java:819) at org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.exists(FileChangedManager.java:151) at org.netbeans.modules.masterfs.filebasedfs.utils.FileInfo.exists(FileInfo.java:112) at org.netbeans.modules.masterfs.filebasedfs.utils.FileInfo.isConvertibleToFileObject(FileInfo.java:173)
Created attachment 148889 [details] stacktrace
a cyclic symlink?
No symlinks in that tree except a single one in my root folder.
(In reply to athompson from comment #3) > No symlinks in that tree except a single one in my root folder. Can you please provide a sketch of your directory structure (showing where the symlink is located and where it is pointing, and the intended project root folder)? Can you reproduce the bug easily? (Every time you try to create new project in that folder?) Thank you very much.
home Shared --> Library/Mobile Documents/com~apple~CloudDocs/Shared dev projects -test (project root) IIRC I had just deleted an HTML5 project of the same name and location before creating the new one. Honestly, I wouldn't worry about it. It just happened that one time, and it could be an issue with running Yosemite beta.
(In reply to athompson from comment #5) > home > Shared --> Library/Mobile Documents/com~apple~CloudDocs/Shared > dev > projects > -test > (project root) I guess this symlink is indeed not related to the exception. > IIRC I had just deleted an HTML5 project of the same name and location > before creating the new one. This could have caused the problem. > Honestly, I wouldn't worry about it. It just happened that one time, and it > could be an issue with running Yosemite beta. I cannot reproduce the issue on Windows. I'll try to reproduce on Linux or Mac later. Thank you for help.
I'm sorry, I cannot reproduce this bug on Mac with directory structure you described. > Honestly, I wouldn't worry about it. It just happened that one time, and it could be > an issue with running Yosemite beta. OK, I'm decreasing priority of this bug. Thank you.
> > Honestly, I wouldn't worry about it. It just happened that one time, and it > > could be an issue with running Yosemite beta. > I cannot reproduce the issue on Windows. I'll try to reproduce on Linux or Mac > later. I haven't been able to reproduce the bug on Mac. Closing the issue.