[jira] [Updated] (NETBEANS-6001) Yaml parser eats memory up to 100% in case of syntax errors
[
https://issues.apache.org/jira/browse/NETBEANS-6001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guntram Blohm updated NETBEANS-6001:
Description:
When editing a YAML file, if there is a syntax error, netbeans eats up memory
until it reaches 100% of what it's assigned, at which point garbage collection
will use all CPU resources and netbeans becomes unresponsive.
To reproduce:
Create a new empty YAML file in any project
Enter the following text into the file:
{{some key:}}
{{ some value: "this is the value"}}
At this point, watch the widget that shows Netbeans' memory consumption, it
increases rapidly, until it reaches 100%. At this point, Java spends 99% of its
time in garbage collection, Netbeans becomes unresponsive (and if the Java
parameters permit using all cores, the system becomes sluggish as well).
Closing/correcting the yaml file at that point doesn't help. This does/did not
happen in Netbeans 12.3.
I attached JProfiler to the JVM that was running netbeans and could confirm the
memory usage increase starting right after entering the invalid yaml. Taking a
heap dump showed 56 million instances of
`org.netbeans.modules.csl.spi.DefaultError`, as well as 56 million
`java.lang.String`s.
was:
When editing a YAML file, if there is a syntax error, netbeans eats up memory
until it reaches 100% of what it's assigned, at which point garbage collection
will use all CPU resources and netbeans becomes unresponsive.
To reproduce:
Create a new empty YAML file in any project
Enter the following text into the file:
{{some key:}}
{{ some value: "this is the value"}}
At this point, watch the widget that shows Netbeans' memory consumption, it
increases rapidly, until it reaches 100%. At this point, Java spends 99% of its
time in garbage collection, Netbeans becomes unresponsive (and if the Java
parameters permit using all cores, the system becomes sluggish as well).
Closing/correcting the yaml file at that point doesn't help.
I attached JProfiler to the JVM that was running netbeans and could confirm the
memory usage increase starting right after entering the invalid yaml. Taking a
heap dump showed 56 million instances of
`org.netbeans.modules.csl.spi.DefaultError`, as well as 56 million
`java.lang.String`s.
> Yaml parser eats memory up to 100% in case of syntax errors
> ---
>
> Key: NETBEANS-6001
> URL: https://issues.apache.org/jira/browse/NETBEANS-6001
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 12.4
> Environment: Netbeans 12.4
> Java jdk-16.0.1+9 from AdoptOpenJDK
> Ubuntu 20.04
> Both Netbeans and the JDK installed from their respective websites, not the
> Ubuntu packet manager
>
>
>Reporter: Guntram Blohm
>Priority: Major
>
> When editing a YAML file, if there is a syntax error, netbeans eats up memory
> until it reaches 100% of what it's assigned, at which point garbage
> collection will use all CPU resources and netbeans becomes unresponsive.
> To reproduce:
> Create a new empty YAML file in any project
> Enter the following text into the file:
> {{some key:}}
> {{ some value: "this is the value"}}
>
> At this point, watch the widget that shows Netbeans' memory consumption, it
> increases rapidly, until it reaches 100%. At this point, Java spends 99% of
> its time in garbage collection, Netbeans becomes unresponsive (and if the
> Java parameters permit using all cores, the system becomes sluggish as well).
>
> Closing/correcting the yaml file at that point doesn't help. This does/did
> not happen in Netbeans 12.3.
>
> I attached JProfiler to the JVM that was running netbeans and could confirm
> the memory usage increase starting right after entering the invalid yaml.
> Taking a heap dump showed 56 million instances of
> `org.netbeans.modules.csl.spi.DefaultError`, as well as 56 million
> `java.lang.String`s.
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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] [Updated] (NETBEANS-6001) Yaml parser eats memory up to 100% in case of syntax errors
[
https://issues.apache.org/jira/browse/NETBEANS-6001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guntram Blohm updated NETBEANS-6001:
Description:
When editing a YAML file, if there is a syntax error, netbeans eats up memory
until it reaches 100% of what it's assigned, at which point garbage collection
will use all CPU resources and netbeans becomes unresponsive.
To reproduce:
Create a new empty YAML file in any project
Enter the following text into the file:
{{some key:}}
{{ some value: "this is the value"}}
At this point, watch the widget that shows Netbeans' memory consumption, it
increases rapidly, until it reaches 100%. At this point, Java spends 99% of its
time in garbage collection, Netbeans becomes unresponsive (and if the Java
parameters permit using all cores, the system becomes sluggish as well).
Closing/correcting the yaml file at that point doesn't help.
I attached JProfiler to the JVM that was running netbeans and could confirm the
memory usage increase starting right after entering the invalid yaml. Taking a
heap dump showed 56 million instances of
`org.netbeans.modules.csl.spi.DefaultError`, as well as 56 million
`java.lang.String`s.
was:
When editing a YAML file, if there is a syntax error, netbeans eats up memory
until it reaches 100% of what it's assigned, at which point garbage collection
will use all CPU resources and netbeans becomes unresponsive.
To reproduce:
Create a new empty YAML file in any project
Enter the following text into the file:
{{some key:}}
{{ some value: "this is the value"}}
At this point, watch the widget that shows Netbeans' memory consumption, it
increases rapidly, until it reaches 100%. At this point, Java spends 99% of its
time in garbage collection, Netbeans becomes unresponsive (and if the Java
parameters permit using all cores, the system becomes sluggish as well).
I attached JProfiler to the JVM that was running netbeans and could confirm the
memory usage increase starting right after entering the invalid yaml. Taking a
heap dump showed 56 million instances of
`org.netbeans.modules.csl.spi.DefaultError`, as well as 56 million
`java.lang.String`s.
> Yaml parser eats memory up to 100% in case of syntax errors
> ---
>
> Key: NETBEANS-6001
> URL: https://issues.apache.org/jira/browse/NETBEANS-6001
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 12.4
> Environment: Netbeans 12.4
> Java jdk-16.0.1+9 from AdoptOpenJDK
> Ubuntu 20.04
> Both Netbeans and the JDK installed from their respective websites, not the
> Ubuntu packet manager
>
>
>Reporter: Guntram Blohm
>Priority: Major
>
> When editing a YAML file, if there is a syntax error, netbeans eats up memory
> until it reaches 100% of what it's assigned, at which point garbage
> collection will use all CPU resources and netbeans becomes unresponsive.
> To reproduce:
> Create a new empty YAML file in any project
> Enter the following text into the file:
> {{some key:}}
> {{ some value: "this is the value"}}
>
> At this point, watch the widget that shows Netbeans' memory consumption, it
> increases rapidly, until it reaches 100%. At this point, Java spends 99% of
> its time in garbage collection, Netbeans becomes unresponsive (and if the
> Java parameters permit using all cores, the system becomes sluggish as well).
>
> Closing/correcting the yaml file at that point doesn't help.
>
> I attached JProfiler to the JVM that was running netbeans and could confirm
> the memory usage increase starting right after entering the invalid yaml.
> Taking a heap dump showed 56 million instances of
> `org.netbeans.modules.csl.spi.DefaultError`, as well as 56 million
> `java.lang.String`s.
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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] [Created] (NETBEANS-6001) Yaml parser eats memory up to 100% in case of syntax errors
Guntram Blohm created NETBEANS-6001:
---
Summary: Yaml parser eats memory up to 100% in case of syntax
errors
Key: NETBEANS-6001
URL: https://issues.apache.org/jira/browse/NETBEANS-6001
Project: NetBeans
Issue Type: Bug
Affects Versions: 12.4
Environment: Netbeans 12.4
Java jdk-16.0.1+9 from AdoptOpenJDK
Ubuntu 20.04
Both Netbeans and the JDK installed from their respective websites, not the
Ubuntu packet manager
Reporter: Guntram Blohm
When editing a YAML file, if there is a syntax error, netbeans eats up memory
until it reaches 100% of what it's assigned, at which point garbage collection
will use all CPU resources and netbeans becomes unresponsive.
To reproduce:
Create a new empty YAML file in any project
Enter the following text into the file:
{{some key:}}
{{ some value: "this is the value"}}
At this point, watch the widget that shows Netbeans' memory consumption, it
increases rapidly, until it reaches 100%. At this point, Java spends 99% of its
time in garbage collection, Netbeans becomes unresponsive (and if the Java
parameters permit using all cores, the system becomes sluggish as well).
I attached JProfiler to the JVM that was running netbeans and could confirm the
memory usage increase starting right after entering the invalid yaml. Taking a
heap dump showed 56 million instances of
`org.netbeans.modules.csl.spi.DefaultError`, as well as 56 million
`java.lang.String`s.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5781) Priming gradle build does not honor the gradle version set in Options/Java/Gradle
[ https://issues.apache.org/jira/browse/NETBEANS-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17388838#comment-17388838 ] Guntram Blohm commented on NETBEANS-5781: - Adoptopenjdk 16.0.1 on Ubuntu 20.04. Both AdoptOpenJdk and Netbeans installed from download, not by the Ubuntu package manager. > Priming gradle build does not honor the gradle version set in > Options/Java/Gradle > - > > Key: NETBEANS-5781 > URL: https://issues.apache.org/jira/browse/NETBEANS-5781 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 12.4 > Environment: Ubuntu 20.04, AdoptOpenjdk 16.0.1, Netbeans 12.4. JDK > and Netbeans were installed by downloads, not by the Ubuntu package manager. > >Reporter: Guntram Blohm >Assignee: Laszlo Kishalmi >Priority: Major > Labels: gradle, version > Attachments: Screenshot_2021-06-15_11-31-49.png > > > When opening a gradle project, Netbeans does not honor the gradle version set > in Tools/Options/Java/Gradle, instead, it seems to always use gradle 7.0.0. > I have an older project that uses deprecated features, so it needs gradle > 4.10.2 to load. Even when I set "Use Standard Gradle Version" to "4.10.2", > Netbeans uses gradle 7 to load the project, decides it can't, and makes the > project unusable. Pressing the "hammer" button (F11) to build the project > correctly uses Gradle 4.10.2 and builds the project. > Attached screenshot shows, after "reload project", how Netbeans uses Gradle > 7.0 even with gradle 4.10.2 selected in Options. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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] [Created] (NETBEANS-5781) Priming gradle build does not honor the gradle version set in Options/Java/Gradle
Guntram Blohm created NETBEANS-5781: --- Summary: Priming gradle build does not honor the gradle version set in Options/Java/Gradle Key: NETBEANS-5781 URL: https://issues.apache.org/jira/browse/NETBEANS-5781 Project: NetBeans Issue Type: Bug Components: projects - Gradle Affects Versions: 12.4 Environment: Ubuntu 20.04, AdoptOpenjdk 16.0.1, Netbeans 12.4. JDK and Netbeans were installed by downloads, not by the Ubuntu package manager. Reporter: Guntram Blohm Assignee: Laszlo Kishalmi Attachments: Screenshot_2021-06-15_11-31-49.png When opening a gradle project, Netbeans does not honor the gradle version set in Tools/Options/Java/Gradle, instead, it seems to always use gradle 7.0.0. I have an older project that uses deprecated features, so it needs gradle 4.10.2 to load. Even when I set "Use Standard Gradle Version" to "4.10.2", Netbeans uses gradle 7 to load the project, decides it can't, and makes the project unusable. Pressing the "hammer" button (F11) to build the project correctly uses Gradle 4.10.2 and builds the project. Attached screenshot shows, after "reload project", how Netbeans uses Gradle 7.0 even with gradle 4.10.2 selected in Options. -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-4452) The Plugin Installer found problem timeout of loading C/C++ Remote Development API[org.netbeans.modules.cnd.api.remote/1.29.5.1] while install the following plugins:
[
https://issues.apache.org/jira/browse/NETBEANS-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17182000#comment-17182000
]
Guntram Blohm commented on NETBEANS-4452:
-
I can confirm that temporarily switching to JDK 8 solves the problem. Madiha
Shabbir, you need to make netbeans use the older JDK by (temporarily) changing
{{netbeans_jdkhome=/path/to/jdk_8}} in {{/path/to/netbeans/etc/netbeans.conf.}}
> The Plugin Installer found problem timeout of loading C/C++ Remote
> Development API[org.netbeans.modules.cnd.api.remote/1.29.5.1] while install
> the following plugins: C++
> -
>
> Key: NETBEANS-4452
> URL: https://issues.apache.org/jira/browse/NETBEANS-4452
> Project: NetBeans
> Issue Type: Bug
> Components: cnd - Other
>Affects Versions: 12.0, 11.3
>Reporter: Mauro Mauri
>Priority: Blocker
> Fix For: Next
>
>
> "The Plugin Installer found problem timeout of loading C/C++ Remote
> Development API[org.netbeans.modules.cnd.api.remote/1.29.5.1] while install
> the following plugins:
> C/C++"
> This error occurred when I install C++ plugin, at the end of installation, so
> the plugin is not installed. Netbeans 8.2 enabled, it's the same with
> releases 11.3 and 12.0.
> I had no problems with 11.0 release.
> Any idea ? Thank you
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-2464) Netbeans 8.2's C/C++ Plugin Install Error Timeout for Loading Module
[
https://issues.apache.org/jira/browse/NETBEANS-2464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17181998#comment-17181998
]
Guntram Blohm commented on NETBEANS-2464:
-
According to [https://stackoverflow.com/a/61637994/3066467,] this is a problem
with newer JDKs not providing unpack200.exe anymore. While their suggestion to
copy that file over from an old jdk to the new one didn't work, temporarily
setting netbeans jdk home to an old 1.8 version did.
> Netbeans 8.2's C/C++ Plugin Install Error Timeout for Loading Module
>
>
> Key: NETBEANS-2464
> URL: https://issues.apache.org/jira/browse/NETBEANS-2464
> Project: NetBeans
> Issue Type: Bug
> Components: utilities - Code
>Affects Versions: 11.0
> Environment: openSUSE Linux 15.0, KDE 5, OpenJDK 10 running on Intel
> Core i5 750 at 2.67 GHz + 8 GB of RAM + AMD Radeon RX 580.
>Reporter: giu.gr
>Priority: Major
> Fix For: 10.0
>
>
> Installing C/C++ plugin does get interrupted throwing an exception.
>
> {code:java}
> INFO [org.netbeans.modules.autoupdate.services.InstallSupportImpl]: Timeout
> waiting for loading module org.netbeans.modules.cnd.api.remote@1.29.5.1
> INFO [org.netbeans.modules.autoupdate.ui.wizards.InstallStep]: timeout of
> loading C/C++ Remote Development
> API[org.netbeans.modules.cnd.api.remote/1.29.5.1]
> org.netbeans.api.autoupdate.OperationException[INSTALL]: timeout of loading
> C/C++ Remote Development API[org.netbeans.modules.cnd.api.remote/1.29.5.1]
> at
> org.netbeans.modules.autoupdate.services.InstallSupportImpl$3.call(InstallSupportImpl.java:429)
> at
> org.netbeans.modules.autoupdate.services.InstallSupportImpl$3.call(InstallSupportImpl.java:289)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1135)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> {code}
>
> Netbeans 8.2's C/C++ plugin used to work in Netbeans 10.0.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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
