High CPU during log playback

Report bugs found in TunerPro. Please be sure to include as much info as possible, including system specs, OS, repro steps and TunerPro version number.

Moderators: Mangus, robertisaar, dex

Post Reply
festy
Posts: 25
Joined: Thu May 17, 2012 3:25 pm
Location: Oz

High CPU during log playback

Post by festy »

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?...
User avatar
Mangus
TunerPro Author
Posts: 1918
Joined: Wed Mar 19, 2003 1:49 pm

Post by Mangus »

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)
***************************************
TunerPro Author
1989 Trans Am
festy
Posts: 25
Joined: Thu May 17, 2012 3:25 pm
Location: Oz

Post by festy »

That would explain it!

Edit - 8202 looks great, thanks 8)
The1
Posts: 33
Joined: Wed Jul 20, 2011 2:41 am

Post by The1 »

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
festy
Posts: 25
Joined: Thu May 17, 2012 3:25 pm
Location: Oz

Post by festy »

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.

Code: Select all

  Problem Event Name&#58;	AppHangB1
  Application Name&#58;	TunerPro.exe
  Application Version&#58;	5.0.8202.0
  Application Timestamp&#58;	52329b21
  Hang Signature&#58;	2920
  Hang Type&#58;	0
  OS Version&#58;	6.1.7600.2.0.0.256.1
  Locale ID&#58;	3081
The1
Posts: 33
Joined: Wed Jul 20, 2011 2:41 am

Post by The1 »

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)
Could this be put back in future versions as an option, perhaps checkbox?
Post Reply