This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Steps: - create io application - start application - type in terminal something, enter - click on CPU usage Actual: Opened CPU time per function window with content: Looking for the most CPU consuming functions...
Created attachment 82778 [details] log+threads dump
Looks like we are no so good in messaging here, as "Looking for the most CPU consuming functions..." means that we do not have data, but user can think if any they will appear automatically which is wrong, to update data you should click on the indicator
In addition to the confusing message, I see a few usability problems in the CPU Time Per Function tab. There is a time interval selection, and a refresh button. I can't figure out how they can logically coexist. To me, a refresh capability implies measurement of an ongoing activity, and a time interval implies looking at something that has already happened, and a refresh has no meaning in that context. So they should not both be functional at the same time. Suggestions: Can the Refresh button be disabled once the user selects a time interval? Can we have the Refresh button show up in that moment before there is CPU function time to display, so the user can click Refresh instead of clicking the Hot Spots button again? It does not seem intuitive to me to click the indicator button again after the tab is opened. Can we have a message somewhere, maybe in the blank area next to the Clear Selection button, which says "Click the Refresh button to update this display" ? The Refresh button needs a tooltip that says "Refresh the display". If it is always the case that the message and data will not be refreshed/updated without user action, the message should be "Looking for functions with high CPU time, but no data is available yet. Click Refresh." Or if we cannot have the Refresh button show up here: "Looking for functions with high CPU time, but no data is available yet. Click Hot Spots again."
We should be able to select an interval which is bounded only from "beginning" to see data starting from specific point and in this case "Refresh" will be actual.
Fixed in http://hg.netbeans.org/cnd-main/rev/5eeeb82c75e1 and http://hg.netbeans.org/cnd-main/rev/ef8daa8ca673 Susan, please verify the new behavior and messages.
Integrated into 'main-golden', will be available in build *200910221401* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/5eeeb82c75e1 User: Alexey Vladykin <alexey_vladykin@netbeans.org> Log: Fixing #166009 Bad messaging in Profile Deatils View