eCtune

If you load a big datalog that takes a while, eCtune will crash if you select Graphs before the loading finishes. I would suggest a progress bar or something to let the user know this might take a few seconds. Easy to reproduce.... Start ectune. load calibration. Load (big) logfile. Press Grahps immediately before load is complete. I see this with any of the recent 0.0.2.0 releases; I have noticed it before too but forgot to report it, sorry /Allan

mail me a big log file please

fixed

If you close a datalog without closing the graphs window, it crashed sometimes as well if you try and reopen a different log.

please post exact steps.

Do a run Save Datalog Disconnect Logging Open Log File Open Graphs Window Close Log File but leave Graphs window open Open different or same log file Crash Not always...but lots of times. Could be due to the size of the log...but I'm not certain.

if you have a log that does it can u send it?

calvin wrote:if you have a log that does it can u send it?

Next time it happens I will try and remember to send the stuff. In a middle of a tune though, you know how it goes...

is still an open issue. Reporter please get back to me.. See if u can find a datalog that does it so i can debug.. I would like to close all open bugs...

It happens on every datalog to me now... I can open two or three different logs and then it starts causing errors. Doesnt matter the log file...after the 3rd log I open (after 3 runs) it starts doing it pretty constantly and I have to restart eCtune. As soon as I restart, its fine for a little...and then happens again.

I have found that closing the datalog graph will lessen it... I normally close the graph window, then close the log, then load a new one. I have not been able to get exact steps for mine yet... it keeps doing it at different times.

so if i leave the graph window open and open 3 different log files it should crash?

JaredKaragen wrote:I have found that closing the datalog graph will lessen it... I normally close the graph window, then close the log, then load a new one. I have not been able to get exact steps for mine yet... it keeps doing it at different times.

I concur... If I forget to close the graph and/or forget to close the open log file before reconnecting, it increases the chance that eCtune will error out. When I make a log, I hit record...do the pull. Save log file. Disconnect datalogging. Open Log file. Open Graphs window...analyze, go back and forth between windows and make my changes. Close graph window, close log file. Reconnect to datalogging... Lots of time on that reconnect is where I get the severe crash and eCtune has to be force quit (that fucking sucks when I forgot to save)

i'll try to simulate the problem

I have found that if you do not close the graph window, it happens twice as much. If it errors and you \"continue\", it will show a big x over the graph window (not every time, but most of the time) Then close and reopen the graphs window and it will show normal. Sometimes it gets stuck in a forever loop of asking for you to hit continue; then you must close it, but if you highlight the continue button, then hover over the quicksave button, hit enter then click right after, you can get in a save request to not loose your work. Calvin, I just tried to get it to bug out... loading a million logs, closing the window, not closing the window... nothing. I'll try some more tonight.