You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@netbeans.apache.org by "Jan van Oosterom (Jira)" <ji...@apache.org> on 2022/03/14 09:24:00 UTC

[jira] [Comment Edited] (NETBEANS-3283) POM graph creation freezes NetBeans

    [ https://issues.apache.org/jira/browse/NETBEANS-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17506088#comment-17506088 ] 

Jan van Oosterom edited comment on NETBEANS-3283 at 3/14/22, 9:23 AM:
----------------------------------------------------------------------

on big projects with lots of dependencies this freezes Netbeans.

When you wait long enough the graph may complete and the Netbeans will work again.

There is only one cpu in use by Netbeans during 'render'.

Maybe every time the canvas is to small to position the graph its starts over with a bigger canvas?


was (Author: JIRAUSER286563):
on big projects with lots of dependencies this freezes netbeans.

When you wait long enough the graph may complete and the computer will work again.

There is only one cpu in use by netbeans.

Maybe everytime the canvas is to small to position the graph its starts over with a bigger canvas?

> POM graph creation freezes NetBeans
> -----------------------------------
>
>                 Key: NETBEANS-3283
>                 URL: https://issues.apache.org/jira/browse/NETBEANS-3283
>             Project: NetBeans
>          Issue Type: Bug
>          Components: projects - Maven
>    Affects Versions: 11.2
>            Reporter: Alessandro Falappa
>            Priority: Major
>         Attachments: nb-graph-bug-thread-dump.txt
>
>
> NetBeans freezes when creating the graph of dependencies for a NetBeans Plugin maven project.
> Steps:
> * Clone [https://github.com/AlexFalappa/nb-springboot.git]
> * Open {{pom.xml}} file
> * Click on _Show Graph_
> The JVM process running NetBeans consumes about 30-40% of CPU but the UI is completely frozen with no other option than terminate NetBeans from the OS process manager.
> Took a stacktrace dump of the process (attached) but I am not sure how to diagnose the problem.
> The problematic part could be:
> {code}
> "AWT-EventQueue-0" #23 prio=6 os_prio=0 cpu=774656.25ms elapsed=18594.28s tid=0x000000002a2af800 nid=0x3a9c runnable  [0x000000002b87c000]
>    java.lang.Thread.State: RUNNABLE
> 	at java.util.Collections$UnmodifiableCollection$1.hasNext(java.base@11.0.4/Collections.java:1046)
> 	at org.netbeans.modules.java.graph.FruchtermanReingoldLayout.isThereFreeSpaceNonFixedSpace(FruchtermanReingoldLayout.java:351)
> 	at org.netbeans.modules.java.graph.FruchtermanReingoldLayout.relayoutNonFixed(FruchtermanReingoldLayout.java:391)
> 	at org.netbeans.modules.java.graph.FruchtermanReingoldLayout.doRelayoutNonFixed(FruchtermanReingoldLayout.java:371)
> 	at org.netbeans.modules.java.graph.FruchtermanReingoldLayout.performLayout(FruchtermanReingoldLayout.java:117)
> 	at org.netbeans.modules.java.graph.FruchtermanReingoldLayout.performLayout(FruchtermanReingoldLayout.java:69)
> 	at org.netbeans.api.visual.layout.SceneLayout$LayoutSceneListener.sceneValidated(SceneLayout.java:100)
> 	at org.netbeans.api.visual.widget.Scene.validate(Scene.java:378)
> 	at org.netbeans.modules.java.graph.DependencyGraphScene.highlightDepth(DependencyGraphScene.java:691)
> 	at org.netbeans.modules.maven.graph.DependencyGraphTopComponent.maxPathSpinnerStateChanged(DependencyGraphTopComponent.java:468)
> 	at org.netbeans.modules.maven.graph.DependencyGraphTopComponent.access$1100(DependencyGraphTopComponent.java:97)
> 	at org.netbeans.modules.maven.graph.DependencyGraphTopComponent$9.stateChanged(DependencyGraphTopComponent.java:431)
> 	at javax.swing.JSpinner.fireStateChanged(java.desktop@11.0.4/JSpinner.java:461)
> 	at javax.swing.JSpinner$ModelListener.stateChanged(java.desktop@11.0.4/JSpinner.java:388)
> 	at javax.swing.AbstractSpinnerModel.fireStateChanged(java.desktop@11.0.4/AbstractSpinnerModel.java:120)
> 	at javax.swing.SpinnerNumberModel.setMaximum(java.desktop@11.0.4/SpinnerNumberModel.java:278)
> 	at org.netbeans.modules.maven.graph.DependencyGraphTopComponent$10$3.run(DependencyGraphTopComponent.java:636)
> 	at java.awt.event.InvocationEvent.dispatch(java.desktop@11.0.4/InvocationEvent.java:313)
> 	at java.awt.EventQueue.dispatchEventImpl(java.desktop@11.0.4/EventQueue.java:770)
> 	at java.awt.EventQueue$4.run(java.desktop@11.0.4/EventQueue.java:721)
> 	at java.awt.EventQueue$4.run(java.desktop@11.0.4/EventQueue.java:715)
> 	at java.security.AccessController.doPrivileged(java.base@11.0.4/Native Method)
> 	at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(java.base@11.0.4/ProtectionDomain.java:85)
> 	at java.awt.EventQueue.dispatchEvent(java.desktop@11.0.4/EventQueue.java:740)
> 	at org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:136)
> 	at java.awt.EventDispatchThread.pumpOneEventForFilters(java.desktop@11.0.4/EventDispatchThread.java:203)
> 	at java.awt.EventDispatchThread.pumpEventsForFilter(java.desktop@11.0.4/EventDispatchThread.java:124)
> 	at java.awt.EventDispatchThread.pumpEventsForHierarchy(java.desktop@11.0.4/EventDispatchThread.java:113)
> 	at java.awt.EventDispatchThread.pumpEvents(java.desktop@11.0.4/EventDispatchThread.java:109)
> 	at java.awt.EventDispatchThread.pumpEvents(java.desktop@11.0.4/EventDispatchThread.java:101)
> 	at java.awt.EventDispatchThread.run(java.desktop@11.0.4/EventDispatchThread.java:90)
> {code}
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@netbeans.apache.org
For additional commands, e-mail: commits-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists