Page 2 of 2
Re: Huge TunerStudioAppDebug.txt file
Posted: Fri Jun 23, 2017 12:54 pm
by LT401Vette
BigBlockMopar wrote:Just shooting an idea here; Maybe incorporate a log-rule that prevents writing to the log, if the newest message is the same as the last one (except for the timestamp).
And perhaps then occassionally show a log-entry that the last error message occured n-number of times in a period of x-seconds.
That does sound like a reasonable idea.
While I'm not sure what action triggered the repeated error, it is not hard for an error to happen in a loop. Global protection would good.
Re: Huge TunerStudioAppDebug.txt file
Posted: Fri Jun 23, 2017 1:59 pm
by jsmcortina
Sounds like it should trigger a user warning and/or a process reset too for improved application reliability.
James
Re: Huge TunerStudioAppDebug.txt file
Posted: Sat Jul 22, 2017 5:10 am
by jsmcortina
I've just seen similar behaviour in 3.0.27 that could cause a very large log file.
22/07/17 13:07:29 :Info: Opening port: /dev/ttyUSB0
22/07/17 13:07:29 :Info: Error creating streams to port, closing port to cleanup.
22/07/17 13:07:29 :Info: Error closing port on cleanup. Port name - /dev/ttyUSB0; Method name - closePort(); Exception type - Port not opened.
22/07/17 13:07:29 :Debug: Port not valid: Unable to open port: /dev/ttyUSB0
Please check your Communications Settings.
...
on and on and on...
The file is growing by 59k every minute.
James