[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16788560#comment-16788560 ] Eric Bresie commented on NETBEANS-168: -- Were any of the items I mentioned previously related? > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 3.5h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16776689#comment-16776689 ] michael anderl commented on NETBEANS-168: - All I wrote was with the new new Gradle support, but i think it hat problems with my old .gradle and .nb-gradle files. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 3.5h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16776648#comment-16776648 ] Geertjan Wielenga commented on NETBEANS-168: Yes, in Apache NetBeans 11, new Gradle support is included, please only test with that, not with the old Gradle module which is completely different. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 3.5h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16776644#comment-16776644 ] michael anderl commented on NETBEANS-168: - After removing the .gradle and .nb-gradle files from my gradle project and killing all the java processes (I think left over from gradle) after a restart the problem is gone. I used the old gradle Module on the project. Now with NB-master with gradle I dont need it any more. I try to reproduce it with the old .gradle .nb-gradle files. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 3.5h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16775814#comment-16775814 ] michael anderl commented on NETBEANS-168: - do you want the dump with some special combination? nb 11-vc01 or master or nb10 build with sun corretto run with openjdk 12-33 or 11? > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 3.5h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16775492#comment-16775492 ] Ivan Friedländer commented on NETBEANS-168: --- [~andler] 1.8GB is a lot, but try to increase the size of the heap, whether it does not help. -J-Xmx3072m to nb_folder/etc/netbeans.conf [~lkishalmi] if you have a lot of work, I can look at that heap dump > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 3.5h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16775450#comment-16775450 ] Laszlo Kishalmi commented on NETBEANS-168: -- Can you compress the heapdump and upload to this Telegram Group: [https://t.me/joinchat/BdL4NxZckuEhDP9pYSQLlQ] I gues it would be too large to be attached to this Jira ticket. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 3.5h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16775432#comment-16775432 ] Ivan Friedländer commented on NETBEANS-168: --- Without access to the heapdump, the cause can not be identified. But I assume it is not related to this issue. ??Same here:?? ??fresh userdir and cachedir and a fresh installation of nb (git master) and nbjavac 1.51 afterwards?? ??when i open a big gradle subproject with many java files (1778 java files in 21 folders) the background scanning of projects goes fast to 99% and stops (ui starts to freeze)?? ??after a while and freeze i get some outofmemoryerrors: java heap space?? ??got to kill nb with the task manager?? ??in userdir/var/log/heapdump.hprof is about 1,8gb big.?? ??this happens every time i open the project?? ??thx?? ??mike?? > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 3.5h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16775367#comment-16775367 ] michael anderl commented on NETBEANS-168: - Same here: fresh userdir and cachedir and a fresh installation of nb (git master) and nbjavac 1.51 afterwards when i open a big gradle subproject with many java files (1778 java files in 21 folders) the background scanning of projects goes fast to 99% and stops (ui starts to freeze) after a while and freeze i get some outofmemoryerrors: java heap space got to kill nb with the task manager in userdir/var/log/heapdump.hprof is about 1,8gb big. this happens every time i open the project thx mike *Product Version:* Apache NetBeans IDE Dev (Build 20190221-fa6d3a548783) --> ( compiled with amazon-corretto-8.202.08.2 and ANT 1.10.5 ) *Java:* 12; OpenJDK 64-Bit Server VM 12+33 *Runtime:* OpenJDK Runtime Environment 12+33 *System:* Windows 7 version 6.1 running on amd64; UTF-8; de_AT (nb) *User directory:* D:\01NB\userdir12 *Cache directory:* D:\01NB\cachedir12 java.lang.OutOfMemoryError: Java heap space at java.base/java.util.Arrays.copyOf(Arrays.java:3746) at java.base/java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:172) at java.base/java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:775) at java.base/java.lang.StringBuilder.append(StringBuilder.java:248) at java.base/jdk.internal.reflect.MethodAccessorGenerator.generateName(MethodAccessorGenerator.java:756) at java.base/jdk.internal.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:286) at java.base/jdk.internal.reflect.MethodAccessorGenerator.generateSerializationConstructor(MethodAccessorGenerator.java:112) at java.base/jdk.internal.reflect.ReflectionFactory.generateConstructor(ReflectionFactory.java:520) at java.base/jdk.internal.reflect.ReflectionFactory.newConstructorForSerialization(ReflectionFactory.java:512) at java.base/java.io.ObjectStreamClass.getSerializableConstructor(ObjectStreamClass.java:1516) at java.base/java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:509) at java.base/java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:484) at java.base/java.security.AccessController.executePrivileged(AccessController.java:750) at java.base/java.security.AccessController.doPrivileged(AccessController.java:310) at java.base/java.io.ObjectStreamClass.(ObjectStreamClass.java:484) at java.base/java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:381) at java.base/java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1135) at java.base/java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:349) at org.netbeans.modules.uihandler.AfterRestartExceptions.save(AfterRestartExceptions.java:129) at org.netbeans.modules.uihandler.AfterRestartExceptions.schedule(AfterRestartExceptions.java:92) at org.netbeans.modules.uihandler.UIHandler.publish(UIHandler.java:149) at java.logging/java.util.logging.Logger.log(Logger.java:979) at java.logging/java.util.logging.Logger.doLog(Logger.java:1006) at java.logging/java.util.logging.Logger.log(Logger.java:1117) at org.netbeans.core.NbLifecycleManager.exit(NbLifecycleManager.java:212) at org.netbeans.core.NbLifecycleManager.exit(NbLifecycleManager.java:115) at org.netbeans.core.windows.view.ui.MainWindow$9.windowClosing(MainWindow.java:529) at java.desktop/java.awt.AWTEventMulticaster.windowClosing(AWTEventMulticaster.java:357) at java.desktop/java.awt.AWTEventMulticaster.windowClosing(AWTEventMulticaster.java:357) at java.desktop/java.awt.AWTEventMulticaster.windowClosing(AWTEventMulticaster.java:357) at java.desktop/java.awt.AWTEventMulticaster.windowClosing(AWTEventMulticaster.java:357) at java.desktop/java.awt.Window.processWindowEvent(Window.java:2068) > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 3.5h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16773820#comment-16773820 ] Wolfgang Reder commented on NETBEANS-168: - Yesterday I started a new project within an new git repository. Everything worked fine, until the first git-push. Now, my NB is as busy as with every other (older) project. My OS is Linux amd64 with openjdk11 and nb10 > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 3.5h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16773782#comment-16773782 ] Ivan Friedländer commented on NETBEANS-168: --- The / tmp directory generates many events that are unnecessary for NB. And it can happen that some application will start to generate huge file changes and get it in the same state as with broken links. Perhaps it would be sufficient to indicate the overloading of the file-event system to make the user aware that there is a problem.. Currently, it is processor overloaded, but the user does not know what's going on. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 3.5h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16773379#comment-16773379 ] Laszlo Kishalmi commented on NETBEANS-168: -- Unfortunately that's not the cause. There are many plugins especially the vcs which are using /tmp regularly for storing some temporary revisions of a file to display diffs, etc. But do watching on /tmp changes is not bad thing at all. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 3.5h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16773108#comment-16773108 ] Marc Collin commented on NETBEANS-168: -- with gradle, when i start netbeans in /tmp nb-gradle-plugin folder is created maybe it's for that this dir is watched > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 3.5h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769421#comment-16769421 ] Laszlo Kishalmi commented on NETBEANS-168: -- Well, actually it would be good that somebody would take a jdk 12 and profile netbeans with another netbeans on windows. Until nobody steps up for that, we are just hitting the air. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 3.5h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769163#comment-16769163 ] Ivan Friedländer commented on NETBEANS-168: --- I agree with it, it will cause any broken link. The condition is that the directory which contains that link is watched by NB Filesystem. And so far I have not been able to find out why it will start watching /tmp dir. This can cause performance problems. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 3.5h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769134#comment-16769134 ] Christian Lenz commented on NETBEANS-168: - But again, it is not only about gradle. I don't use gradle for example. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 3.5h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769133#comment-16769133 ] Ivan Friedländer commented on NETBEANS-168: --- It's purely a problem in the NetBeans filesystem. And Gradle contains a bug that triggers it: https://github.com/gradle/gradle/issues/8119 > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 3.5h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769101#comment-16769101 ] Christian Lenz commented on NETBEANS-168: - > 2. We can't really do anything about it, just give some webpage with > recommendations. Why not? I mean we can't be the only one software with that problem. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 3.5h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769098#comment-16769098 ] Laszlo Kishalmi commented on NETBEANS-168: -- Please collect as many data as you could around here! This issue might cover multiple issues. # The ide masterfs does not handle broken symlinks correcly, that triggers a CPU burn # It might be Windows Defender and co. related thing # Maybe something else. As of 1. It usually happens on Linux. and using Gradle (not necessarily in the IDE) can trigger it really quick. A workaround for that is exists in the NB11.0-vc1 and the master. 2. We can't really do anything about it, just give some webpage with recommendations. 3. Need to be explored. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 3.5h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769075#comment-16769075 ] Wolfgang Reder commented on NETBEANS-168: - Hello ! Yesterday i installed the proposed patch (org-netbeans-modules-masterfs-patchs), on both nb installations (NB8.2@JDK8 and NB10.0@JDK11). The problem remains. Can I collect informations to help to solve the problem ? I'ts very annoying to start the IDE every 30 minutes... > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 3.5h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759470#comment-16759470 ] Eric Bresie commented on NETBEANS-168: -- Does this in any way relate to other background process/cpu issues like: # NETBEANS-1864 Background Scanning got stuck # NETBEANS-1939 Silent exception thrown during background scanning of projects # NETBEANS-1629 there is a memory overflow error when background scanning is going on, mainly for large projects/projects within projects or when there are many projects open # NETBEANS-1929 Hangs during the "Background scanning the projects" (resolved) # NETBEANS-1142 Exception when scanning projects # NETBEANS-1668 Netbeans Appears to Become Unresponsive # NETBEANS-1610 Constant background CPU usage # NETBEANS-485 OutOfMemoryError after background scanning of local Maven repository # NETBEANS-416 Excessive CPU usage # > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 2h 20m > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[
https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16746376#comment-16746376
]
Ivan Friedländer commented on NETBEANS-168:
---
As I wrote the problems are two broken links and unix socket files.
The problem with symlinks is that the bad code is in multiple modules. And it's
asynchronous, so it's bad for debugging.
The author of these modules has forgotten that
{code:java}
File.exists()
{code}
uses the FOLLOW_LINKS option. The masterfs linux module takes the status of
files native from linux.
And on multiple places the file is checked with File.exist() and that generates
the file created/deleted loop.
With unix socket files is the is a similar problem from masterfs linux returns
that file exist and File.exist() returns false..
The simplest fix is here
[https://github.com/NBANDROIDTEAM/org-netbeans-modules-masterfs-patches/commit/e485736a1e68f338288be27ced28c1b1506fad5d]
A more complex option is to replace File.exist() to Files.exists(path,
LinkOption.NOFOLLOW_LINKS) in all NB source codes.
And exclude "other files" from NB filesystem..
> Background scanning process needs a rethink
> ---
>
> Key: NETBEANS-168
> URL: https://issues.apache.org/jira/browse/NETBEANS-168
> Project: NetBeans
> Issue Type: Bug
> Components: ide - Performance, java - Platform, platform - Execution
>Affects Versions: 8.2, 9.0, 10.0
> Environment: NetBeans 8.2, Windows 10 x64
>Reporter: Christian Lenz
>Priority: Blocker
> Labels: ca_survey, pull-request-available
> Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0
> vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Often, while cloning, switching branch, merging, opening etc. etc. NetBeans
> starts Background scanning for changes, but it is not real background,
> because everything what you want to do then, like changing the branch,
> commit, push, pull, open project, delete or whatever, is blocking by this
> task and you can't cancel it, because it is essential.
> Either we need to rethink about this process like to make everything or most
> of the stuff doing things in parallel or the task should really be
> cancelable. It is a pain in the ass for big projects when they start to scan
> for changes.
> It is a real world case because you acan see it when you work on NetBeans
> modules.
> Cheers
> Chris
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16746339#comment-16746339 ] Petro commented on NETBEANS-168: [~Chrizzly], as I've noticed above, I had infinite background process scanning. The behavior was the same for different versions of NetBeans and JDK. I've fixed it by removing all broken symlinks from project folder. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 2h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16746244#comment-16746244 ] Geertjan Wielenga commented on NETBEANS-168: So this is specifically this PR then: https://github.com/apache/incubator-netbeans/pull/1061 > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 2h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16746247#comment-16746247 ] Christian Lenz commented on NETBEANS-168: - Yes and maybe [~arsi] can say smth about it, because he already has fixed it in his NBAndroid plugin. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 2h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16746234#comment-16746234 ] Christian Lenz commented on NETBEANS-168: - Sometimes, yes but the main point, what we figured out or more [~lkishalmi] and [~arsi] are some problems with masterFS and some symlinks. I really now that we need specific steps to reproduce and sometimes it is smth different, thats why we are here and discuss such topics as good as possible. If this is not possible, w/o any outcome, sure we can close the other tickets etc. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 2h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[
https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16746167#comment-16746167
]
Geertjan Wielenga commented on NETBEANS-168:
It's quite difficult because each person has their own experience here and in
some (maybe many) cases it's a user error, e.g., the one above:
{quote}But netbeans was so slow and I discovered that java was running as
32-bit while I use netbeans 64-bit. So I looked again at java and unzipped
jdk-11. That solved a lot!!{quote}
I mean, how could we fix the above in NetBeans? We can't it's an error on the
user's side.
> Background scanning process needs a rethink
> ---
>
> Key: NETBEANS-168
> URL: https://issues.apache.org/jira/browse/NETBEANS-168
> Project: NetBeans
> Issue Type: Bug
> Components: ide - Performance, java - Platform, platform - Execution
>Affects Versions: 8.2, 9.0, 10.0
> Environment: NetBeans 8.2, Windows 10 x64
>Reporter: Christian Lenz
>Priority: Blocker
> Labels: ca_survey, pull-request-available
> Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0
> vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Often, while cloning, switching branch, merging, opening etc. etc. NetBeans
> starts Background scanning for changes, but it is not real background,
> because everything what you want to do then, like changing the branch,
> commit, push, pull, open project, delete or whatever, is blocking by this
> task and you can't cancel it, because it is essential.
> Either we need to rethink about this process like to make everything or most
> of the stuff doing things in parallel or the task should really be
> cancelable. It is a pain in the ass for big projects when they start to scan
> for changes.
> It is a real world case because you acan see it when you work on NetBeans
> modules.
> Cheers
> Chris
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16746147#comment-16746147 ] Christian Lenz commented on NETBEANS-168: - I Would like to change this to blocker, because a lot of complaints are out there for that background scanning process. Some solutions are there, but missing some discussion? Not only complaints w/o any info, I try my best to figure it out too and others too. And we have some similar, already linked tickets. If you don't agree with the blocker, please change it back if you think different, with some comments. Thx. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 2h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742932#comment-16742932 ] Christian Lenz commented on NETBEANS-168: - I added some tickets that COULD be related to this ticket too, but not have to. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 2h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741837#comment-16741837 ] flexJoly commented on NETBEANS-168: --- Last week I updated java and now the whole netbeans is a lot faster. I am no java-expert, and was unsure what to use and I could not get it to work fast enough. So I copied the jre from netbeans 8.0. That worked ;-) But netbeans was so slow and I discovered that java was running as 32-bit while I use netbeans 64-bit. So I looked again at java and unzipped jdk-11 That solved a lot!! > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16740421#comment-16740421 ] Christian Lenz commented on NETBEANS-168: - Another little thing is, that this Background scanning task, is one aggressive one, that you can't cancel. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16729766#comment-16729766 ] Ivan Friedländer commented on NETBEANS-168: --- This is a primary emergency solution for Netbeans 8.2 because Gradle produces broken links. For Apache Netbeans I would rather suggest, to exclude broken links and other files "Files.readAttributes (file, BasicFileAttributes.class) .isOther ()" from loading to FileObjects, they are useless. But I spend all my free time to developing of NBANDROID-V2. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Labels: ca_survey > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16729752#comment-16729752 ] Laszlo Kishalmi commented on NETBEANS-168: -- Well, nice catch guys! Can we have some PR-s fixing these issues? > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Labels: ca_survey > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[
https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16729581#comment-16729581
]
Ivan Friedländer commented on NETBEANS-168:
---
There are two problems:
The first is global and is in
org.netbeans.modules.versioning.masterfs.FilesystemInterceptor.deletedExternally(FileObject
fo)
It's called VCSFileProxy.createFileProxy(final FileObject fileObject) and that
method registers a new listener.
It needs to be changed to
VCSFilesystemInterceptor.deletedExternally(VCSFileProxy.createFileProxy(FileUtil.toFile(fo)));
And the other is about broken links in
org.netbeans.modules.masterfs.filebasedfs.fileobjects.FileObjectFactory.issueIfExist(...)
{code:java}
if (parent != null && parent.isValid()) {
if (child != null) {
if (foForFile == null) {
exist = (realExists == -1) ? true : touchExists(file,
realExists);
if (fcb.impeachExistence(file, exist)) {
exist = touchExists(file, realExists);
if (!exist) {
refreshFromGetter(parent,asyncFire);
}
}
assert checkCacheState(true, file, caller);
} else if (foForFile.isValid()) {
exist = (realExists == -1) ? true : touchExists(file,
realExists);
if (fcb.impeachExistence(file, exist)) {
exist = touchExists(file, realExists);
if (!exist) {
refreshFromGetter(parent,asyncFire);
}
}
assert checkCacheState(exist, file, caller);
} else {
//! inconsistence
exist = touchExists(file, realExists);
if (!exist) {
//Problematic test, for broken link is false
refreshFromGetter(parent,asyncFire);
}
}
} else {
{code}
f (!exist) { changed to if (!exist && !Files.isSymbolicLink(file.toPath())) {
And CPU has been quiet since then..
Attention change just this one line, I tried to move it into the method
touchExists, but again it was the result Suspended
Details are here:
[https://github.com/NBANDROIDTEAM/NBANDROID-V2/issues/139]
> Background scanning process needs a rethink
> ---
>
> Key: NETBEANS-168
> URL: https://issues.apache.org/jira/browse/NETBEANS-168
> Project: NetBeans
> Issue Type: Bug
> Components: ide - Performance, java - Platform, platform - Execution
>Affects Versions: 8.2, 9.0, 10.0
> Environment: NetBeans 8.2, Windows 10 x64
>Reporter: Christian Lenz
>Priority: Critical
> Labels: ca_survey
> Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0
> vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z
>
>
> Often, while cloning, switching branch, merging, opening etc. etc. NetBeans
> starts Background scanning for changes, but it is not real background,
> because everything what you want to do then, like changing the branch,
> commit, push, pull, open project, delete or whatever, is blocking by this
> task and you can't cancel it, because it is essential.
> Either we need to rethink about this process like to make everything or most
> of the stuff doing things in parallel or the task should really be
> cancelable. It is a pain in the ass for big projects when they start to scan
> for changes.
> It is a real world case because you acan see it when you work on NetBeans
> modules.
> Cheers
> Chris
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16729014#comment-16729014 ] Christian Lenz commented on NETBEANS-168: - https://github.com/NBANDROIDTEAM/NBANDROID-V2/issues/139 I know this is a 3rd-party plugin and gradle too (I think) but could it be smth similiar? He has a similar problem with symlinks if I understand it right [~lkishalmi] > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Labels: ca_survey > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16723949#comment-16723949 ] flexJoly commented on NETBEANS-168: --- This morning I installed v10-rc5 for windows. It runs nice at first. But my (framework) php-project keeps scanned forever It does not hang netbeans. But it holds at a certain percentage. At the moment it is 25% after restarting netbeans. Before it came to 75% and 85% (between restarts). > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Labels: ca_survey > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720152#comment-16720152 ] Varun Agrawal commented on NETBEANS-168: I face the same issue everyday (even when I just mvn compile using commandline). It makes my IDE hostage. I am on NetBeans 10 if that matters. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Labels: ca_survey > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16704418#comment-16704418 ] Christian Lenz commented on NETBEANS-168: - Hey [~lkishalmi] let me know how I can help here with testing and identifing this problem. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Labels: ca_survey > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16704327#comment-16704327 ] Laszlo Kishalmi commented on NETBEANS-168: -- Well, I have some new findings. For whatever reasons there are a couple of broken symlinks accumulating in my /tmp folder. When one get's deleted for whatever reason NetBeans goes wild delivering the file deletion event. I fear that [~Chrizzly] has a different issue. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Labels: ca_survey > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16681444#comment-16681444 ] Christian Lenz commented on NETBEANS-168: - I also added a little screen capture, where you can see, that while the background scanning is running, I can't search for a file but the project window is showing it. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Labels: ca_survey > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16681141#comment-16681141 ] Christian Lenz commented on NETBEANS-168: - Yes it scans the whole node_modules folder too, because I didn't add the node_modules and bower_components to the ignored files after starting a fresh new NetBeans instance. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Labels: ca_survey > Attachments: messages - 10.0 vc3.log, messages 10.0 vc2.log, > messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16681135#comment-16681135 ] Christian Lenz commented on NETBEANS-168: - I added 2 PHP projects that I opened in NetBeans 10.0 VC3. First it tooks ~15s - 20s until NetBeans opens the projects. The projects have 51.519 Files and 8.126 Folders and are ~500 MB big. I can't add the IDE log, because the background scanning AND the checking for external changes scanning started 10-15min ago. I Use brand new 10.0 VC3, deleted the AppData/Roaming/NetBeans/10 folder and started NetBeans. Will attach the messages.log after it is finished scanning :D. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Labels: ca_survey > Attachments: messages 10.0 vc2.log, messages.log, puls.7z, ui.log, > uigestures 10.0 vc, wp-dms.7z > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16673892#comment-16673892 ] Gili commented on NETBEANS-168: --- [~lkishalmi] What I meant is that if Christian can reproduce his problem on demand (he said he can) then you should be able to VNC into his machine and debug it there. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Attachments: messages 10.0 vc2.log, messages.log, ui.log, uigestures > 10.0 vc > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16673888#comment-16673888 ] Laszlo Kishalmi commented on NETBEANS-168: -- I fear we are talking about different issues. Today finally I got something out of profiler. A File deleted event hit the fan, Which took 100% CPU on otherwise idle IDE. As I'm developing NetBeans in NetBeans it seems the NetBeans Project UI Support gone wild, got responsible for 60% of CPU on: org.netbeans.modules.apisupport.project.ui.ImportantFilesNodeFactory$ImportantFilesChildren.refreshKeys Even if none of the important files node were open in the IDE (though I opened a few in my session). I guess we have listener leak here. There is another candidate with 23% CPU time: org.netbeans.modules.parsing.ui.indexing.errors.ErrorAnnotator$RootAddedDeletedListener.fileDeleted > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Attachments: messages 10.0 vc2.log, messages.log, ui.log, uigestures > 10.0 vc > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16673176#comment-16673176 ] Christian Lenz commented on NETBEANS-168: - I know that anti virus like my old one and now the windows defender smartscreen can be a problem in terms of performance (Starting time, background scanning, etc.) but that first means, that no one of our NetBeans windows users, uses any antivirus, or? And this part I can't understand at all. Of those X 1000 users of NetBeans I can't be the only one who has an anti virus. And the other part is that I don't have any problem with VS Code or IntelliJ and now I'm comparing a blank intelliJ and a blank VS Code (counting by hand those less plugins I installed at IntelliJ and VS Code) with a blank NetBeans. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Attachments: messages 10.0 vc2.log, messages.log, ui.log, uigestures > 10.0 vc > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16672753#comment-16672753 ] Christian Lenz commented on NETBEANS-168: - [~cowwoc] I think so, yes. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Attachments: messages 10.0 vc2.log, messages.log, ui.log, uigestures > 10.0 vc > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16672088#comment-16672088 ] Gili commented on NETBEANS-168: --- Christian, are you able to reproduce the issue on demand on your computer? > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Attachments: messages 10.0 vc2.log, messages.log, ui.log, uigestures > 10.0 vc > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16672048#comment-16672048 ] Laszlo Kishalmi commented on NETBEANS-168: -- Well, the real issue is really hard to catch, not even debug that. What happens with me is that sometimes the IDE starts to peg the CPU checking for external modifications. It is also can result heavy GC and sometimes a memory leak. I just don't know how to trigger that. But it happens with me almost daily. Most of the time the IDE is restored itself in 20-30 minutes of heavy disk and CPU work. As of the source scanning it is just really matter of milliseconds, seconds maybe. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Attachments: messages 10.0 vc2.log, messages.log, ui.log, uigestures > 10.0 vc > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16672015#comment-16672015 ] Gili commented on NETBEANS-168: --- Perhaps you could could set up a VNC session where Laszlo could remotely debug the problem on the environment where it occurs? This should help you reproduce the problem faster than this blind-debugging technique :) > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Attachments: messages 10.0 vc2.log, messages.log, ui.log, uigestures > 10.0 vc > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16671883#comment-16671883 ] Laszlo Kishalmi commented on NETBEANS-168: -- Unfortunately this is not enough. I could not reproduce this issue, upon this. It would be still the Windows defender which slows the IDE down. Though there must be an issue somewhere. Yesterday I got a OOME while the IDE was checking for external changes. I run my IDE with my FileChangeListener tweaks for whole night. Nothing happened. I still do not know how to trigger this massive FCL event flow, but keep on trying. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Attachments: messages 10.0 vc2.log, messages.log, ui.log, uigestures > 10.0 vc > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[
https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670688#comment-16670688
]
Christian Lenz commented on NETBEANS-168:
-
And here we are again. Brand new NetBeans 10.0 VC2, with new user dir. Opening
incubator-netbeans/platform/core.multitabs. Opening was okish but background
scanning ran for ~5min. I attached the messages.log and uigestures again. As
you can see in the messages.log, at EOF: {code}INFO
[org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Complete
indexing of 73 source roots took: 273.798 ms (New or modified files: 2.297,
Deleted files: 0) [Adding listeners took: 5 ms]{code}
Windows Defender SmartScreen is running, nothing more.
> Background scanning process needs a rethink
> ---
>
> Key: NETBEANS-168
> URL: https://issues.apache.org/jira/browse/NETBEANS-168
> Project: NetBeans
> Issue Type: Bug
> Components: ide - Performance, java - Platform, platform - Execution
>Affects Versions: 8.2, Next
> Environment: NetBeans 8.2, Windows 10 x64
>Reporter: Christian Lenz
>Priority: Critical
> Attachments: messages.log, ui.log
>
>
> Often, while cloning, switching branch, merging, opening etc. etc. NetBeans
> starts Background scanning for changes, but it is not real background,
> because everything what you want to do then, like changing the branch,
> commit, push, pull, open project, delete or whatever, is blocking by this
> task and you can't cancel it, because it is essential.
> Either we need to rethink about this process like to make everything or most
> of the stuff doing things in parallel or the task should really be
> cancelable. It is a pain in the ass for big projects when they start to scan
> for changes.
> It is a real world case because you acan see it when you work on NetBeans
> modules.
> Cheers
> Chris
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16663822#comment-16663822 ] Christian Lenz commented on NETBEANS-168: - And the impact of the running background scanning process is that it blocks a run command for a maven based NetBeans module and Go To File missing some files, but they are alreaday there and searchable inside of the projects window. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Attachments: messages.log, ui.log > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662785#comment-16662785 ] Christian Lenz commented on NETBEANS-168: - In the ui.log (Which I also attached) you can see some javascript2 module stuff. This happens, because before restart of NetBeans, I had 2 PHP projects opened in the IDE, but I closedd them, because of a known stack overflow, but this is really not the problem. NetBeans still doing Background scanning and when I click on it, I see that he is indexing or scanning the incubator-netbeans folder. So please have a look into the logs, there should be now everything inside, what you need. And Steps to reproduce are above. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Attachments: messages.log, ui.log > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662777#comment-16662777 ] Christian Lenz commented on NETBEANS-168: - After restarting the IDE, I also got a slowness detection notification. Will attach all the information here. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Attachments: messages.log > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662776#comment-16662776 ] Christian Lenz commented on NETBEANS-168: - There are also some exceptions inside, I don't know whether it is related to that or not. Have 3 projects open. Maven Projects which I mentioned before, Maven Grammar (.../java/maven.grammar) and MultiTabs (.../platform/core.multitabs) > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Attachments: messages.log > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16662775#comment-16662775 ] Christian Lenz commented on NETBEANS-168: - I come up with this problem again. I attached my messages.log. What I did: - Clean NetBeans 10.0 VC1 - Open Project/Module Maven Projects (Incubator-netbeans/java/maven) - Appeared the first time, I opened the project - Appears again, after restarting NetBeans > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Attachments: messages.log > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16648953#comment-16648953 ] Christian Lenz commented on NETBEANS-168: - [~lkishalmi] sounds really great Thx for the explanation. I really appreciate your work. Doesn't matter what you did or not :) > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16648731#comment-16648731 ] Laszlo Kishalmi commented on NETBEANS-168: -- Well I guess this can be caused by miss behaving plugins and maybe some edge cases. I'm seeing something similar after waking up from sleep and editing the files. the IDE starts to eat 200%-300% CPU, though remain usable. Though after a while (it can be even 30 minutes) the processor usage become normalized. I was able to attach a profiler to the IDE while this was happening. It seems there is something fishy around the FileObjects and FileChange listeners. The IDE was actually burning CPU on File.isFile and File.isDirectory methods. So plugins registering FileChangeListeners non-carefully could trigger this issu. Though it might be something wrong on the FCL implementation. If my time allows I try to craft some monitoring around this. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16635092#comment-16635092 ] Christian Lenz commented on NETBEANS-168: - I deactived my scanner after I created the ticket, that NetBeans needed more than 3 min to start. It was the scanner obvious, but for this, no scanner is activated anymore. I'm fine for the moment, that you resolve it, can come back later, if I have a proper environment to test. If anyone else can give a testcase, do it. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16634858#comment-16634858 ] Laszlo Kishalmi commented on NETBEANS-168: -- I'm about to mark this issue resolved, if we could not really move forward identifying the real problem. Please also check if it is not some virus/security scanner that are making FS slow. The other day I've just installed NetBeans 9.0 from it's zip distribution, unpacking the zip took more than half an hour on a very stuffed up computer with NVMe drive, due to some Virus scanner scanned each and every file sequentially. It's a shame. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16611766#comment-16611766 ] Geertjan Wielenga commented on NETBEANS-168: How come am I able to work on the Apache NetBeans sources if the above is true. Please, stop responding to issues, stop sending more e-mails. Instead, set up Apache NetBeans 9.0 from scratch, fresh user directory, reproduce the problem, try different JDKs to see if that makes a difference, and then come back here and provide clear step by step problems to reproduce the problem. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[
https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16611729#comment-16611729
]
Christian Lenz commented on NETBEANS-168:
-
{quote}
Just clone the incubator-netbeans project and open it(some modules only) with
Netbeans, you will see the behavior Christian Lenz is talking about.
{quote}
or
{quote}
After adding to existing PHP project JS library MathJax
(https://github.com/mathjax/MathJax) background scanning of projects newer ends
and hungs up NetBeans.
{quote}
is not good enough?
> Background scanning process needs a rethink
> ---
>
> Key: NETBEANS-168
> URL: https://issues.apache.org/jira/browse/NETBEANS-168
> Project: NetBeans
> Issue Type: Bug
> Components: ide - Performance, java - Platform, platform - Execution
>Affects Versions: 8.2, Next
> Environment: NetBeans 8.2, Windows 10 x64
>Reporter: Christian Lenz
>Priority: Critical
>
> Often, while cloning, switching branch, merging, opening etc. etc. NetBeans
> starts Background scanning for changes, but it is not real background,
> because everything what you want to do then, like changing the branch,
> commit, push, pull, open project, delete or whatever, is blocking by this
> task and you can't cancel it, because it is essential.
> Either we need to rethink about this process like to make everything or most
> of the stuff doing things in parallel or the task should really be
> cancelable. It is a pain in the ass for big projects when they start to scan
> for changes.
> It is a real world case because you acan see it when you work on NetBeans
> modules.
> Cheers
> Chris
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16611726#comment-16611726 ] Geertjan Wielenga commented on NETBEANS-168: Guessing is not good. Provide step by step instructions to reproduce a problem and then, only then, can it be worked on. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16611716#comment-16611716 ] Christian Lenz commented on NETBEANS-168: - Sure we will, but when I can guess, the process of the background scanning not changed. For sure, I will test it there too. Maybe [~deferenty] can help here too. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16611712#comment-16611712 ] Geertjan Wielenga commented on NETBEANS-168: Stop using 8.2 use 9.0 instead: https://netbeans.apache.org/download/index.html Then see: https://blogs.apache.org/netbeans/entry/what-s-happened-to-my Gj > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16611704#comment-16611704 ] Petro commented on NETBEANS-168: Have the same problem. After adding to existing PHP project JS library MathJax ([https://github.com/mathjax/MathJax)] background scanning of projects newer ends and hungs up NetBeans. *Product Version:* NetBeans IDE 8.2 (Build 201705191307) *Updates:* NetBeans IDE is updated to version [NetBeans 8.2 Patch 2|http://wiki.netbeans.org/NetBeans8.2PatchesInfo] *Java:* 1.8.0_161; Java HotSpot(TM) 64-Bit Server VM 25.161-b12 *Runtime:* Java(TM) SE Runtime Environment 1.8.0_161-b12 *System:* Linux version 4.4.0-134-generic running on amd64; UTF-8; en_US (nb) > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16589041#comment-16589041 ] Gilberto C Andrade commented on NETBEANS-168: - Just clone the incubator-netbeans project and open it with Netbeans, you will see the behavior [~Chrizzly] is talking about. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521974#comment-16521974 ] Christian Lenz commented on NETBEANS-168: - Will try to find a big OSS project to test it with this. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521975#comment-16521975 ] Christian Lenz commented on NETBEANS-168: - Could be PHP related or smth else. Only guessing. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521368#comment-16521368 ] Laszlo Kishalmi commented on NETBEANS-168: -- Well, there is no movement for some time on this issue. Could we get a sample project, where we could demonstrate this? It could be any open source project big enough. So it would be good if there would be something we could analyze. I tried switching between branches in netbeans git repo, but the background scanning never took more than 2 seconds. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16310067#comment-16310067 ] Christian Lenz commented on NETBEANS-168: - This is normal as for IntelliJ, PHPStorm and Webstorm but only at the beginning, when you open the IDE and the indexing is running and you open the projects. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16310036#comment-16310036 ] Gili commented on NETBEANS-168: --- That's a good point. It's not clear why background scanning is blocking these tasks. I would only expect it is (implicitly) block things like Find Usage or anything that requires to be aware of classes it had not yet parsed. And in those cases, I think I would actually prefer Find Usages to simply not find results (perhaps warn that results might be stale until scanning completes) as opposed to explicitly block the request. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16310020#comment-16310020 ] Christian Lenz commented on NETBEANS-168: - I don't know, I only use IntelliJ or WebStorm or PHPStorm to test smth but not hours. I switch back to NetBeans. So I have to try PHPStorm for our legacy PHP code base. Some versions ago, it was not really possible to open multiple projects which are independent from each other. So I have now 18 Projects in NetBeans open at the same time. 2 PHP, 1 is really big. 2 gradle projects, some HTML5 projects, some Maven Projects and so on. So that is not really a problem for PHPStorm, but I can check it back with the IDE. I think one problem is, that I can have multiple projects open at the same time (of course there are a lot of benefits and I use it everyday). But when I can commit and push, why I need a background scanning? Because it was possible, but this action is holding in line. I don't know the solution for that "problem" only to let everyone know, that this is a bottleneck. I have to wait a long range of time. I can open my command line and can push/pull w/o waiting. Of course there is no need to do anything else, but there shouldn't be nothing else before, when I can commit, pull, push from the IDE. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309943#comment-16309943 ] Gili commented on NETBEANS-168: --- [~Chrizzly] Not downplaying your point, but have your seen any other IDE handle this differently? As I mentioned above, I believe Intellij is doing the same. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309309#comment-16309309 ] Christian Lenz commented on NETBEANS-168: - It is not blocking the IDE, but it is blocking the interaction. When you have multiple big projects and they need a background scan for whatever reasons, the other actions are in the queue like cloning, commit, pushing, pulling, etc. they will not doing stuff in parallel or the background action is blocking all of the other actions. When I did smth I don't know atm and I want to commit or push it NOW, the background scan is blocking the whole action. After sometimes 30s or how long the background scanning process is running, it ends (sometimes, sometimes later) and the other actions in the queue can executed immediately. This behaviour is unacceptable. I can't do some actions until the background scanning ends. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309122#comment-16309122 ] Gili commented on NETBEANS-168: --- Assuming the cache could be updated transactionally, couldn't Netbeans use the previous cache snapshot until the new one is committed? > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
