Playing back logs in the latest Tuner Pro RT build seems to hog the CPU, consuming 100% of a core for the duration of playback.
I've tried multiple logs created with different ADXs and it's the same with all of them.
Win7 x64 dual core, Tuner Pro RT build 5.00.8200.00
Is it just me?...
High CPU during log playback
Moderators: Mangus, robertisaar, dex
I did change the way the logging loop yields its spare time for other processes, which increases TunerPro's logging playback resolution to <1ms. I'll change it back to the way it was, which yields more time for other processes, but results in <15ms resolution by default.
(Fixed in build 8202)
(Fixed in build 8202)
***************************************
TunerPro Author
1989 Trans Am
TunerPro Author
1989 Trans Am
im having the same issue, but mine is freezing to the point where you cannot use it and a single core is maxed out. Happens with any ADX or log file and happens with both 8200 and 8202.
I can only reproduce it on mine when i play with the zoom slider bar on the monitor window, it will do it then or if it doesn't it will as soon as you goto do something else.
Win7x64 here, let me know if you need any other info
I can only reproduce it on mine when i play with the zoom slider bar on the monitor window, it will do it then or if it doesn't it will as soon as you goto do something else.
Win7x64 here, let me know if you need any other info
I can trigger this by switching to the item list view if I moved the time range slider on the Monitor window prior to switching views.
Moving the slider doesn't immediately cause a problem by itself though.
And it's not just high CPU, TP immediately becomes unresponsive and doesn't recover.
Moving the slider doesn't immediately cause a problem by itself though.
And it's not just high CPU, TP immediately becomes unresponsive and doesn't recover.
Code: Select all
Problem Event Name: AppHangB1
Application Name: TunerPro.exe
Application Version: 5.0.8202.0
Application Timestamp: 52329b21
Hang Signature: 2920
Hang Type: 0
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 3081
Could this be put back in future versions as an option, perhaps checkbox?Mangus wrote:I did change the way the logging loop yields its spare time for other processes, which increases TunerPro's logging playback resolution to <1ms. I'll change it back to the way it was, which yields more time for other processes, but results in <15ms resolution by default.
(Fixed in build 8202)