Comments
1 comment
-
Hi,
Thanks for the feedback again - I asked around about this yesterday, the responsiveness problem seems to be related to the number of points on the timeline and its redraw rate, we should get this fixed before the final release (hopefully a lot sooner
)
I'm not 100% sure this will work but in the short term zooming in on the timeline (the mouse wheel is the only way this functionality is exposed right now) might well help cut down the amount of CPU being used by the UI.
I think that Jason, Usman and Stephen are working on trying to reproduce an inhouse test case similar to your code to try and reproduce the other behaviour you are seeing.
With respect to the view not changing or updaing then this could well be due to the processing time required to build up the different trees.. I think in the original build we released there were no "green spinnys" showing processing progress - I'm not sure they are all in the new build but there are a few more in there...
Equally the lack of results changing could well be down to some buggy code so I will ask our testers to look into this as well..
Once again thanks for the bug reports and feedback - its all a great help,
James
Add comment
Please sign in to leave a comment.
Changing from Top Down, to Top Down Abridged has not effect on anything.
-- Press STOP on profiler, now CPU usage has dropped to 0, memory usage still staying at 80,564k
interface is now responsive but results are still incorrect
the results grid is refreshing each time I select a region, but it is refreshing with same incorrect data each time, regardless of how little or how much is selected
I am also seeing strange painting events happing on the 'Method' area, it is drawing the gradient colours for the Time % and Time with children (looks pretty, reminds me of college), when waving mouse pointer over grid it redraws correctly.
also tried to change from CPU Clock to Wall Clock - no effect.
hope this is all beneficial