Another instance already running?

[gman247]

First off, nice little app. Not frilly, no bloat, and does what it's supposed to! I found Core Temp because the All CPU Meter gadget from http://addgadget.com/all_cpu_meter/ uses it to display the temps of my cores. Thanks for releasing it free!

I have 2 issues though. I'm using Win7 x64. The first issue is the same one that's already been reported and worked on where it throws up a million little error messages when coming back from standby.

The 2nd issue which is the focus of this thread is I sometimes get a message of "Another instance of Core Temp is already running". I believe it happens when I lock windows (ctrl-alt-del and then press space), then another user logs on, does work, logs off, and then I resume my session again. My account is an admin acct and the other user is a normal acct.

Core Temp continues to run fine after clicking the button on the error.

Pretty sure it has something to do with how core temp "starts with windows". Maybe it's set up so it starts with each user login instead of really starting with windows before any user logs in?

I've attached a screenshot of the setting page, I figure that would be easier than just trying to type them all Thanks in advance for looking at this, let me know if there's any questions you have for me.

ct-01.jpg

[The Coolest]

Uncheck "Only allow a single instance of Core Temp".

[gman247]

Ok, I'll give it a shot. I figured that it would try to open another instance of it though so there would be 2 running instead of throwing the error. I'll test it out and report back, it doesn't seem to happen all the time which is odd, so I'll have to keep an eye on it.
Thanks!

[gman247]

Ok, that didn't take long Yeah, it started 2 instances of CT when I logged back into the already running session. (2 icons in the systray) Interesting enough it only seems to start 2 instances. If I follow the steps below multiple times it doesn't start a new instance every time, just once so there's only ever 2 running.

Here's the steps to reproduce:
1. Be logged in as a user.
2. Hit ctrl-alt-del then hit space to "lock" the session.
3. Click switch user button and log into a different user.
4. log off that user.
5. log back in to the first user's locked session.

CT will start another instance of itself. The same thing will probably happen if you just directly switch users instead of locking the session but I haven't tested that yet.

[The Coolest]

Well this is less of a Core Temp issue, and more a Windows issue.
Windows is supposed to be able to tell whether a task is already running, it shouldn't launch a second instance of Core Temp if there is an active instance already.
I doubt there's much I can do about this problem.

[gman247]

If you dont mind me asking, whats the mechanism for CT to run at startup? I looked in the registry in the usual places and cant seem to find it? Thanks again.

[gman247]

Never mind, found it. Using the task scheduler, didn't think to look there initially, most programs just use HKLM/Software/Microsoft/Windows/run.

I'm pretty sure I know what the problem is. CT crashed after the multiple error message bug when coming back from standby. Then I manually restarted it.

It looks like the task scheduler option of only allowing 1 instance only applies if task scheduler itself starts the program. So if you manually start it, then the task scheduler is triggered to start it later, it allows the task to run since it doesn't have a record of the first task running.

Maybe an easy solution to this would be to add a checkbox in the CT settings to disable the message box saying another instance is already running so it just silently doesn't run? It's not a huge bug I know, but I just dont like error boxes popping up

I'll leave it up to you if you want to do anything about it or not. Personally I can live with it if need be, just thought you'd like to get a final report from me about it. Thanks again for the quick replies!

[The Coolest]

Sure.
Since Windows Vista, UAC blocks programs that require administrator privileges and are set to autostart.
The workaround for this is to create a scheduled task to make Windows run the application automatically when the user logs in.
If you look around in Task Scheduler you'll find a "Core Temp Autostart" task, it's responsible for starting Core Temp with Windows.

That's a good idea, I'll get this worked into the next release.

[The Coolest]

Ok, basically - done.
If the checkbox is checked for single instance, any attempt to execute core temp again will result in the previous instance being displayed on screen.
It will only display the message box in case it couldn't find the Core Temp window, like in case it is running under a different user account.

[gman247]

Awesome.. That's a better solution than mine Anxiously awaiting the next release for the bugfixes!

[The Coolest]

Check it out and let me know how it works.
http://www.alcpu.com/CoreTemp
v. 0.99.7.7

[Bill_Bright]

I hate dredging up old threads, but since I am running W7 64-bit, and getting the same problem every time I reboot, I thought I would post here. I say every time now, but has done it for a couple years, but only sporadically. It did not bother me because I only reboot when some update forces it - just letting W7 go into hybrid sleep mode. So I may go for weeks without seeing the error. So it is a tiny annoyance at best. But then again, a tiny gnat can be pretty annoying too!

"Allow multiple Core Temp instances" is, and always has been unchecked.

I also use the CT Gadget - but not sure if that is an issue.

V1.0 RC4

I am not a Registry expert, but I do know my way around it fairly well, and don't see where it is being told to run more than once. Not in the Start menu either.

I am going to uninstall and reinstall and see what happens.

[The Coolest]

There must be two copies of Core Temp on your system. One is probably being ran from the task scheduler and the second from the "startup" menu.
When you see the messagebox with the instance message, open task manager, go to processes, sort by name. Then you can right click each Core Temp.exe instance and click on Open file location. That's an easy and quick way to find the duplicate and get rid of it.

[Bill_Bright]

There must be two copies of Core Temp on your system. One is probably being ran from the task scheduler and the second from the "startup" menu.

I looked carefully for a second instance. I just verified there is nothing in scheduler and as I noted above, nothing in the Start menu.

I'll have more time to look at later - I cannot reboot reboot right now.

[Bill_Bright]

Okay - I have spent some more time on this.

I uninstalled CT and rebooted. I got not errors, and no CoreTemp. That "suggests" to me (I'm an electronics technician, not a programmer) there was not two CoreTemps installed on my system.

I installed CT again and rebooted. No problems. So at this point, I don't know if the problem is gone, of if we are back to where it only happens every once in awhile.

Will keep you posted if it happens again.

BTW - thanks for your fast response!

[The Coolest]

No problem. Glad that it's sorted now.
Well the only guess I have is that you might've had some extra entry for starting Core Temp somewhere...
Most importantly is that the problem is gone.

[Bill_Bright]

As long as it stays away, I'm happy. Thanks again.

Happy Holidays!