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 201310012201) VM: Java HotSpot(TM) 64-Bit Server VM, 24.45-b08, Java(TM) SE Runtime Environment, 1.7.0_45-b18 OS: Windows 7 User Comments: GUEST: Working on a Maven Java project. Renaming some packages in the src/main/resources. Getting "can't rename because scanning or project". GUEST: Blocking wen scanning web maven module alied: after a while running and editing the IDE gets sluggish. background scanning of projects keeps even after I closed the project Stacktrace: org.netbeans.modules.parsing.impl.indexing.ScanCancelledException: Slow scanning in text/javascript at java.lang.Thread.getStackTrace(Thread.java:1588) at org.netbeans.modules.parsing.impl.indexing.LogContext.create(LogContext.java:131) at org.netbeans.modules.parsing.impl.indexing.LogContext.create(LogContext.java:124) at org.netbeans.modules.parsing.impl.indexing.PathRegistry.scheduleFirer(PathRegistry.java:829) at org.netbeans.modules.parsing.impl.indexing.PathRegistry.resetCacheAndFire(PathRegistry.java:822) at org.netbeans.modules.parsing.impl.indexing.PathRegistry.access$500(PathRegistry.java:86)
Created attachment 143692 [details] stacktrace
This bug already has 5 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=203899
Due to the last report I'm moving this to php.
Sorry but parsing PHP files bigger than 5MB is not allowed and is forbidden in code. Can you try to create empty php project (no features like versioning etc.) and put there that big file? It shouldn't be parsed. Run NB with this option: -J-Dorg.netbeans.modules.php.editor.parser.Logger.level=FINE You can also mail me that file...zipped to obrejla@netbeans.org Thanks.
(In reply to Ondrej Brejla from comment #4) > Sorry but parsing PHP files bigger than 5MB is not allowed and is forbidden > in code. Can you try to create empty php project (no features like > versioning etc.) and put there that big file? It shouldn't be parsed. > > Run NB with this option: > -J-Dorg.netbeans.modules.php.editor.parser.Logger.level=FINE > > You can also mail me that file...zipped to obrejla@netbeans.org Thanks. Hi, You probably understood me wrong - it is *.html file (not PHP) which contains log with PHP errors. I've tried creating an empty project and putting this *.html file inside - the same problem occurred. I will email you this file zipped. Hope it will help to get rid of this bug :)
Ok, reassigning to html.
(In reply to Ondrej Brejla from comment #6) > Ok, reassigning to html. Email sent. Hope it will help.
Created attachment 144986 [details] Big file Hmm, I tried that in the dev build and file is parsed properly in few secs (file attached)...no endless scanning. The only thing in the log is JS parser exception. It will be fixed by ppisl. So this is "works for me". You can try the dev build... or you have some strange setup, hard to say. Try to make "fresh" instal, with clean userdir and no old settings imported.
(In reply to Ondrej Brejla from comment #8) > Created attachment 144986 [details] > Big file > > Hmm, I tried that in the dev build and file is parsed properly in few secs > (file attached)...no endless scanning. The only thing in the log is JS > parser exception. It will be fixed by ppisl. So this is "works for me". > > You can try the dev build... or you have some strange setup, hard to say. > Try to make "fresh" instal, with clean userdir and no old settings imported. I will try it in a few hours. Will install NetBeans on a fresh PC. If it will work for me too, I'll try to compare both IDE settings.
I have fixed the js parser exception noted by Ondra.
(In reply to Ondrej Brejla from comment #8) > Created attachment 144986 [details] > Big file > > Hmm, I tried that in the dev build and file is parsed properly in few secs > (file attached)...no endless scanning. The only thing in the log is JS > parser exception. It will be fixed by ppisl. So this is "works for me". > > You can try the dev build... or you have some strange setup, hard to say. > Try to make "fresh" instal, with clean userdir and no old settings imported. I've tried clean installs with 7.4 and nightly build. 7.4 - bug exists NB - no bug So I believe it will be fixed in a new release.
Created attachment 145892 [details] stacktrace a
So what else remains to be done here?
seems the issue has been already fixed