Exiting TS - JAVAW.exe

[Stag76]

I've removed the old versions, then installed the latest JRE and TS V0.988.7a, and it is still leaving multiple versions of JAVAW.exe running when I exit - 1 for each time I start TS. I'm running it on a Laptop and a Notebook, both with the same symptoms. Is anybody else experiencing this, or have I installed something incorrectly.

[LT401Vette]

What OS are you running?
Can you send your TunerStudioLogFile.txt from your install dir?

[kritip]

I run it on XP and Vista, and often find existing ones running. I sometimes notice it as TS slows down as so much memory is in use. Sometime one is running, I opemn up TS and it won't connect (comms issue), so i quit and kill the other process.

Sometimes it won't autoupdate because one is running in the background.

Doesn't really cause me any issues though, i just kill the processes when they hang around.

/edit - for example, i just downloaded the latest update via TS, it restarted, but hadn't updated. A javaw.exe was still running. Kill it off, loaded up TS and it had updated itself

[LT401Vette]

I have seen a couple people report that happening, especially causing the auto update problem. But I haven't been able to reproduce it to figure out what it is hanging on. If your new instance won't connect, until you go and kill the javaw, It must be hanging on either killing the comm thread and closing the port or somewhere before that.

Is there any Exception in the TunerStudioLogFile.txt?

What type of serial connection are you using?

Does it seem to hang every time? Just if you are connected to a controller? Most times? If you have made changes to you tune?

[kritip]

I use an ftdi usb adapter, very relaible though, and i used to have the same thing happen on a windows2k laptop with a real serial port.

Attached is my log. You can see the two loads withthe older version, then i killed the javaw.exe, and relaoded it and the new version was applied.

Nothing actually "hangs" though, TS still runs fine, but it either won't connect, or won't update. When it doesn't connect due to it, it is a bit odd though, as it still initialises ok when it loads up.

It is hard to reproduce though. I can see what is leaving processes behind personally.

If you have a debug version, that does a lot more logging, i woul dbe happy to run that if it's going to help you?

CHeers,

Kristian

[LT401Vette]

Oh it is hanging... The app may not be stuck on the screen, but that javaw is TunerStudio, so it is probably getting stuck after I hide the window. There is still some clean up work after that, so it would be normal to take a few seconds after the window disappears for javaw to exit.

Looking at your log, it looks like it exited each time. So is it exiting right now?

Is it perhaps at certain times it starts not exiting repeatedly.. Something that came to me as I type, if auto update is running, it will block exiting to try to prevent interrupting a download. This includes while it is just checking for an update. So... If Auto Update has not successfully checked with my server for an update in 7 days, it will do so when you first start the app. It should be a short check in the background, taking 5-10 seconds if you are connected to the internet, if not connected it will just give up. I'm wondering if maybe there is some circumstance that causes it to never mark the update check complete, so when you go to exit it will just hang waiting. I'll have a look in there.

[kritip]

Yes, working fine at the moment, I keep trying to recreate it, but it's behaving itself lol

[LT401Vette]

Tricky little devil

[Stag76]

TunerStudioLogFile.zip attached.

[LT401Vette]

I see it happening in that log... It is not the auto update though, it looks to be hanging on close project.

My guess is that if instead of closing the app, you just close the project, it will either hang or perhaps give some strange results when you reopen the project.

I may need to do a build with extra debug info, there is a lot going on between that last message: "Removing Configuration XXX" and the actual close of the app.

I could just put a timeout thread, so if it didn't come back after X, I just chop it at the knees, but then there would still be issues with the incomplete cleanup if you close the project without closing the app.

[LT401Vette]

I think I may have found something.....
If you exit the app using the Menu:
File--> Exit

If is not calling the same shut down routine.... It is getting rid of the app, but several threads keep hanging on in the background...

If you close using the X in the top right corner, it is running the right shut down. I will put out a release with that fixed and a timeout Thread that will dump a bunch of debug info if the app doesn't close within 30 seconds.

[Mario]

I would post my file but it is 2.65GB

Should I delete this file periodically?

[LT401Vette]

2.65 GB! There must be some bad errors going on I there. That file should get deleted on the next start of TS. TS deletes the log file on start up if it is over 5 MB. But there has to be something bad happeneing for of to be getting that big and it may be failing to delete when there is still a javaw hanging.