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.
This issue was reported manually by tzezula. It already has 1 duplicates Build: NetBeans IDE 7.1 RC2 (Build 201111302200) VM: Java HotSpot(TM) Client VM, 21.0-b17, Java(TM) SE Runtime Environment, 1.7.0-b147 OS: Linux User Comments: mkrivan: I wanted to open a quite large php project and the scanning projects stopping at 66% and do not move forward. I have tried many times to repeat it and did not success. Do you have any ideas what can be the problem? How can I solve it? Stacktrace: java.lang.Exception: Scan canceled. at java.lang.Thread.getStackTrace(Thread.java:1567) at org.netbeans.modules.parsing.impl.indexing.LogContext.create(LogContext.java:74) at org.netbeans.modules.parsing.impl.indexing.LogContext.create(LogContext.java:67) at org.netbeans.modules.parsing.impl.indexing.PathRegistry.scheduleFirer(PathRegistry.java:769) at org.netbeans.modules.parsing.impl.indexing.PathRegistry.resetCacheAndFire(PathRegistry.java:764) at org.netbeans.modules.parsing.impl.indexing.PathRegistry.access$500(PathRegistry.java:83)
Created attachment 114253 [details] stacktrace
Not sure why cancel exception occured, maybe something in parsing api? Sorry for reassigning, but I can't see anything somehow connected with php modules.
Now I did some more experiments. First I did clean svn checkout for the project, and I have started in netbeans to construct a clean project from the source. Approximately after 5 minutes the scanning has been successfully finished. I was happy so I extend the project environment as it was before. The main difference is that I use some symbolic link onto the current directory (some kind of environmental distinction). And after adding the directory links, looks that the scanning procedure do not finish any more. The cancel in the log is just done manually after a while I could not wait. So could you think that the symbolic links makes the forever scanning? I see many times this line in the netbeans messeges.log: INFO [org.netbeans.modules.subversion]: Subversion.cleanupTask: Scanning in progress, trying again in 5000ms Did I help with this additional thinking and trial?
I have forgotten to write that the php project includes 12500 files and consume approx. 88 MB. (In reply to comment #3) > Now I did some more experiments. > > First I did clean svn checkout for the project, and I have started in netbeans > to construct a clean project from the source. > > Approximately after 5 minutes the scanning has been successfully finished. I > was happy so I extend the project environment as it was before. > > The main difference is that I use some symbolic link onto the current directory > (some kind of environmental distinction). And after adding the directory links, > looks that the scanning procedure do not finish any more. > > The cancel in the log is just done manually after a while I could not wait. > > So could you think that the symbolic links makes the forever scanning? > > > I see many times this line in the netbeans messeges.log: > > INFO [org.netbeans.modules.subversion]: Subversion.cleanupTask: Scanning in > progress, trying again in 5000ms > > Did I help with this additional thinking and trial?
The cancel exception occured because of human interaction after a long time waiting. The main problem is that the scanning process does not terminate during a long period. (In reply to comment #2) > Not sure why cancel exception occured, maybe something in parsing api? Sorry > for reassigning, but I can't see anything somehow connected with php modules.
I did backward check on the idea written below. And yes. After deleting the symbolic links from the directory the scanning process finished successfully approx. 3 minutes which could be fine. But anyhow perhaps it would be useful if such a symbolic link does not hang up the scanning process. Thanks for your cooperation till now and in advance as well. (In reply to comment #3) > Now I did some more experiments. > > First I did clean svn checkout for the project, and I have started in netbeans > to construct a clean project from the source. > > Approximately after 5 minutes the scanning has been successfully finished. I > was happy so I extend the project environment as it was before. > > The main difference is that I use some symbolic link onto the current directory > (some kind of environmental distinction). And after adding the directory links, > looks that the scanning procedure do not finish any more. > > The cancel in the log is just done manually after a while I could not wait. > > So could you think that the symbolic links makes the forever scanning? > > > I see many times this line in the netbeans messeges.log: > > INFO [org.netbeans.modules.subversion]: Subversion.cleanupTask: Scanning in > progress, trying again in 5000ms > > Did I help with this additional thinking and trial?
The exception is not important at all, it's not an exception is's only record of scan reason (in this case opening the project). The issue is "opening a large php project scanning projects do not finish"
>So could you think that the symbolic links makes the forever scanning? Yes, it can be the reason. The parsing.api handles sym links by some heuristics but the rest does not. So it can be the reason. Can you create some small test project which hangs and share it? Thanks
Created attachment 114264 [details] extremely small project example with two symbolic links Two symbolic links in a project is enough two demonstrate the situation. With one symbolic link only there is no hang up.
The scan of attached project needs to be verified. The parsing.api itself (FileObjectCrawler) has protection agains cycles but the rest does not.
This bug already has 5 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=183843
*** This bug has been marked as a duplicate of bug 207214 ***