Forum Discussion

chrseck's avatar
chrseck
New Member
10 years ago

Bug in Scatter Plot?

Since upgrading to the January 2016 version the scatter plot stopped working. All old reports using it freeze, if I add it to a report, the report stops responding.

The service has the same problem (since mid of January?). There we actually get an error message about a long running script.

 

Anyone else with this problem?

Best

Christoph

Need Help

4 Replies

  • Greg_Deckler's avatar
    Greg_Deckler
    Community Champion
    10 years ago

    chrseck - Hmm, I am not seeing that behavior with the January update to Desktop. I am on Windows 10, Desktop Version: 2.31.4280.361 64-bit (January 2016). I can add scatter charts and reports do not freeze. I can see scatter charts in reports in the Service. What I do not see are scatter charts as dashboard tiles in the Service, those definitely appear to not be working at the moment.

    • chrseck's avatar
      chrseck
      New Member
      10 years ago

      I did some further testing. With very few rows it seems to work. Using DimProductSubcategory is OK.
      With DimProduct I have to wait for some minutes when I drag a field to X-Axis. Adding a field to y-Axis 

      than stops everything again ....

      Task Manager shows CefSharp.BrowserSubProcess as the culprit. 

      The december version has no problems here. 

       

      Best

      Christoph

      • Greg_Deckler's avatar
        Greg_Deckler
        Community Champion
        10 years ago

        chrseck - I did, in fact, have only a couple rows that I was testing with, nice follow-up. yapaxi - my Value is a decimal number and I am using Average, but it is only a few rows of data, about 10.

  • yapaxi's avatar
    yapaxi
    New Member
    10 years ago

    This is not a scatter plot issue.

    In my case it appears when I add aggregations for decimal columns even in default chart (when you click on dataset columns in Field Explorer). Same CefSharp.BrowserSubprocess spinning CPU infinitely.

     

    Previously this bug touched only browser version, but now it comes to desktop too.