VisualVM
  1. VisualVM
  2. VISUALVM-109

VisualVM UI blocked by updating actions

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: Beta 2
    • Fix Version/s: not determined
    • Component/s: code
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      109

      Description

      When selection/selected node(s) properties change in Application window, all
      selection-aware actions update their enabled/disabled state. Since this code is
      performed synchronously in EDT, it could block UI for significant time,
      especially when using JMX connection to resolve the state.

      This is a serious performance problem and should be fixed by updating action
      states in parallel outside of EDT. Probably there could be two types of actions

      • synchronous which update their state immediately and asynchronous updating the
        state lazily.

        Activity

        Hide
        jsedlacek added a comment -

        Created an attachment (id=59)
        Typical threaddump related to the problem

        Show
        jsedlacek added a comment - Created an attachment (id=59) Typical threaddump related to the problem
        Hide
        jsedlacek added a comment -

        Will provide a workaround for 1.0.

        Show
        jsedlacek added a comment - Will provide a workaround for 1.0.
        Hide
        jsedlacek added a comment -

        Workarounded for 1.0, lowering priority. The workaround is based on the fact
        that Overview view for an application always supports opening and saving the
        view - this query on all DataSourceViewProviders caused the most significant
        problems (JMX connection was utilized to compute the result).

        When
        com.sun.tools.visualvm.application.views.overview.ApplicationOverviewViewProvider
        is applicable in context of actual selection,
        DataSourceViewsManager.hasViewsFor(DataSource) and canSaveViewsFor(DataSource,
        Snapshot) immediately returns true.

        Show
        jsedlacek added a comment - Workarounded for 1.0, lowering priority. The workaround is based on the fact that Overview view for an application always supports opening and saving the view - this query on all DataSourceViewProviders caused the most significant problems (JMX connection was utilized to compute the result). When com.sun.tools.visualvm.application.views.overview.ApplicationOverviewViewProvider is applicable in context of actual selection, DataSourceViewsManager.hasViewsFor(DataSource) and canSaveViewsFor(DataSource, Snapshot) immediately returns true.
        Hide
        jsedlacek added a comment -

        Not for 1.0.

        Show
        jsedlacek added a comment - Not for 1.0.

          People

          • Assignee:
            visualvm-issues
            Reporter:
            jsedlacek
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: