High CPU use CLICKING tool tips, HOVER ok

[BigLou240sx]

TS v2.6.04, Java 7U65 (7.0.650.20). Windows 7

Just a small note - the Tool Tip behavior is different when clicking on the Tool Tip question mark button versus hovering over.
Clicking: Yellow background, black text. Choppy, slow, high CPU usage (javaw.exe). Locks TS up for some time; prevents any interaction. Looks like TS is trying to display the older style tool tip bubble text box that had an X button to close (sometimes the exit/X button shows, sometimes it doesn't)
Hovering: Blue background, black text. Smooth, low CPU usage.

I'll learn to just hover to solve this issue, but perhaps for a future TS release, the behavior should be the same by clicking/hovering and/or alleviate the CPU usage when clicking?

As always, love TS/MLV. Keep up the great work.

ETA: Clicking on the notes button next to the tool tip button also provokes a slow response and high CPU usage.

[BigLou240sx]

Is the behavior described above not experienced by other users or able to be replicated?

If not (and I'd be perfectly happy to accept this as an issue with my own machine/install versus TS), is there anything I can try to help solve this issue on my own install or provide additional data for troubleshooting?

[LT401Vette]

I can not reproduce this.
What sort of computer are you using?

[BigLou240sx]

Thanks Phil

I'm using an Acer Aspire One Notebook with a 1.0GHz AMD Dual Core and 4GB RAM, running Win7 Home Premium x64, Java 7U65 (7.0.650.20), and TS TS v2.6.04

Exact model here: http://www.newegg.com/Product/Product.a ... 6834215341

[LT401Vette]

I would think that would be fine.

Gauges move smoothly? I'm wondering if there is a video driver issue.

[BigLou240sx]

I would think that would be fine.

Gauges move smoothly? I'm wondering if there is a video driver issue.

Everything else appears perfect - I've never had any complaints about the dashboard/gauge behavior. I looked into the driver, it apparently is up to date and windows is telling me there is no better driver.

I updated to the latest TS/MLV via the offline .exe installers (without removing old TS/MLV instances or Java, if it matters). Now on TS v2.6.14. I'm still seeing the high CPU behavior. Here are some screenshots to bolster my description:

Hover.jpg

click_first.png

click_eight seconds.png

I will continue to monitor future TS/Java releases and see if/when this subsides on my install. If there's anything else you can recommend looking into, I'll be happy to try them out. Thanks again

ETA: I inadvertently used different tool tips when taking the screenshots; to be clear, I do NOT see the tool tip text change.

[jsmcortina]

I get a similar hang problem on the "notes" and the tooltips look like that last screenshot where the popup didn't display correctly.

James

[Fueler]

I have seen the same issues. I just don't clik on the tip anymore.

[LT401Vette]

This hasn't changed in years, so I'm not sure why some are seeing an issue here now. Maybe a change to the JRE or maybe it just wasn't reported before?
I'm not sure what might be triggering it. It is not reproduced on any of the 7 testing computers here.

But I do know the way I am rendering those is different from anywhere else. This was as it was coded for a 1.5 JRE, there are better ways to accomplish it now.

[jsmcortina]

It has misrendered for me from the beginning I think. I have reported it before.

James

[BigLou240sx]

This hasn't changed in years, so I'm not sure why some are seeing an issue here now. Maybe a change to the JRE or maybe it just wasn't reported before?
I'm not sure what might be triggering it. It is not reproduced on any of the 7 testing computers here.

But I do know the way I am rendering those is different from anywhere else. This was as it was coded for a 1.5 JRE, there are better ways to accomplish it now.

Personally, it was more fresh eyes (I'm a relatively new user... ~2 years) and instead of concentrating on tuning, I was playing around with the new fw/dashboard/tool tips and trying to find my way around adding additional fuel drivers which allowed me to step back and see it (and repeat it without interrupting tuning).

Since you are unable to recreate - please feel free to let me know if there's anything more you want to see that would help out.