2 ProcessGovener.exe running is this normal!

airborne · April 27, 2011, 12:57:28 PM

Hello!
I have 2 ProcessGovener.exe running is this normal i have seen this on all my Vista computers!
Processlasso.exe is also running.
Why is 2 processes with the same running!

Kind Regards

edkiefer · April 27, 2011, 01:16:55 PM

what version are you on and did this happen from a fresh reboot .
I am on 4.09.50 and just looked at my processGoverner.exe was foo somehow . Was on when I updated and I don't see anywhere in log it was shutoff .

airborne · April 27, 2011, 01:31:14 PM

Hello!

I have version 4.00.34.

hanemach_gt · April 27, 2011, 01:39:13 PM

It is very possible there is malware running on your machine rather than bug in Process Lasso.
Please look again at process list and note if there is no space before extension: ProcessGovernor .exe

airborne · April 27, 2011, 01:48:55 PM

They are spelled exactly the same ProcessGovenor.ex. And i have no Malware or virus
i can promise you that. This is not only on my computer i have seen this on 3 computers.
The only thing this computers have incommon is that they are Vista.

Kind Regards

TfH · April 27, 2011, 02:07:54 PM

Quote from: airborne on April 27, 2011, 12:57:28 PMI have 2 ProcessGovener.exe running

I've seen that too sometimes and i forgot to mention it when i noticed it. I don't remember when i noticed it first time.

Killed PL and restarted it solved and other case i had to reboot rig to get only one instance.

Haven't seen two instances in long time now.

airborne · April 27, 2011, 02:31:32 PM

Reboot doesn't help both processes are back at startup!

edkiefer · April 27, 2011, 02:51:07 PM

do you have any setting changed from default like "restart core engine if it stops" .
I guess you could setup instance count on the processgovernor.exe to only 1 .

I have not notice 2 instances so far here but I don't run PL from startup , so that might have something to do with it .

Jeremy Collake · April 27, 2011, 03:04:08 PM

What version are you using? There was a beta build in which this occurred, but I *thought* it had been fixed (and I had not seen it again). Please let me know so I can check if needed. This condition won't actually hurt anything, though obviously isn't desirable. Thanks

airborne · April 27, 2011, 03:04:24 PM

Hello!

The diffrence i see is that my Vista machines has 2 ProcessGuvenor.exe. But my Xp has only one.

Kind Regards

airborne · April 27, 2011, 03:06:10 PM

Maybee system related problem. I have last stabel release 4.00.34 Pro.

Kind Regards

Jeremy Collake · April 27, 2011, 04:50:25 PM

Ok, this is definitely fixed in the latest beta, if you want to switch to it. It is a beta, but that problem is gone. I am getting this version to final as quickly as possible. If there is a delay, I will backport that particular fix and issue another final version. I've tried to avoid that, knowing how close I am to release.

To fix it with the CURRENT final, simply go to the Windows 'Task Scheduler', then find the task for the Process Lasso core engine (processgovernor.exe). Delete it, but NOT the one for the GUI. Alternatively, run the installer again or select 'reconfigure the way Process Lasso starts' in the general options and select not to start the governor at bootup. The GUI will launch it anyway, so it will still get launched. A synchronization/timing anomaly on some boots, on some systems was causing two instances to become active.

airborne · April 27, 2011, 05:04:49 PM

Okey! Thank you for your answer.

Kind regards

edkiefer · April 27, 2011, 11:06:44 PM

Quote from: jeremy.collake on April 27, 2011, 04:50:25 PM
Ok, this is definitely fixed in the latest beta, if you want to switch to it. It is a beta, but that problem is gone. I am getting this version to final as quickly as possible. If there is a delay, I will backport that particular fix and issue another final version. I've tried to avoid that, knowing how close I am to release.

To fix it with the CURRENT final, simply go to the Windows 'Task Scheduler', then find the task for the Process Lasso core engine (processgovernor.exe). Delete it, but NOT the one for the GUI. Alternatively, run the installer again or select 'reconfigure the way Process Lasso starts' in the general options and select not to start the governor at bootup. The GUI will launch it anyway, so it will still get launched. A synchronization/timing anomaly on some boots, on some systems was causing two instances to become active.

Just some more info on my post I made before .ever since 4.09.50 when I start PL processGovernor.exe is not running (I am not getting the pop up window asking how I want it running). GUI opens with a warning core engine is not running and with tray icon all red stoplight . you can simply start it up but this is new issue and was working fine before.
It is repeatable on mine XP SP3 system , just close everything and start PL .

Jeremy Collake · April 28, 2011, 03:35:25 AM

Thanks, that is a little design quirk, will be dealt with very shortly.