Can you check to see if it shows in system tray at start up. It does load up at start up though. Looks to be random.
Yea, I had another report of that. I am investigating it and fixing it in this beta series. Thanks for the report.
Np. Love the program Keeps getting better and better.
I tracked down the cause to another problem when 'Exit GUI on window close' is enabled. Sigh. Can you confirm this?
Thanks
I have had it crash on exit like twice but seems to be fine now. Just have to see if the new fix takes care of it.
I am going to be uploading the new beta in a few minutes, it should take care of the problem. Please let me know how it goes.
I is still doing it. I have not tried the latest beta to see if that fixes it. Have 3.46.2 installed. Will try the latest beta.
Hmm, yes please do let me know how it does. The latest final should have fixed the problem. Perhaps there is something else going on. I will investigate further.
So far so good. I will keep an eye on it to see if it dose it again. You looking into should help too. Keep up the great work.
It just happened with 3.48. I will try 3.48.1 and see what happens.
Ok, thanks. To be clear, are we talking about the crash at exit now or the disappearance of the system tray icon?
Disappearance of the system tray icon when windows starts up.
Ok, I thought so, was just making sure ;). When I had went back and read this thread, it seemed unclear.
I think I may have see this occur once, but am not sure if it was because I had accidentally closed the GUI with 'exit when GUI closed' enabled or not. I haven't seen it occur again. Never fear, I will find out what is going on sooner or later here. It's a strange phenomenon to be sure.
Looks good so far. I just saw new version so will give that a try and keep my eye on it.
Just booted the up this morning and it is not showing.
Quote from: parkd1 on March 02, 2009, 10:09:34 AM
Just booted the up this morning and it is not showing.
Ok, thanks. I'll post here as soon as I've made a fix that I think will work. Until then, I think it's safe to assume that new versions won't fix this bug. I suppose I could accidentally fix it, but that seems unlikely ;o.
It is doing it with version 3.52 too. Thanks.
I'm really sorry I haven't fixed this yet, I just haven't reproduced it. I don't mean to let you down, I hope to figure it out soon. In the meantime, if you disable 'Exit GUI on window close', does everything work as it should? Perhaps that can be a temporary work-around until I finally figure out what in the heck is going on.
A quick series of new questions: I long ago fixed an issue where it disappeared right after startup. Is it now disappearing sometime later than that? Also, when you restart Process Lasso, does it still later disappear? Also, does explorer.exe on your system ever crash? Process Lasso is designed to restore its system tray icon on crashes of explorer, and perhaps that is malfunctioning. Also, did you try an uninstall and reinstall?
You might also try removing the /tray parameter, if it exists, from the HKCU (or HKLM) Windows/CurrentVersion/Run value for Process Lasso. I am experimenting with that now.. giving this whole issue a fresh look. I need to get this fixed up before you get too frustrated with me ;o.
If I'm confused on any details of the problem, or your setup, please correct me, as I've got a lot to keep up with and maybe the issue is I'm misunderstanding the reported trouble. As I understand it: It disappears at startup (only) when 'Exit on GUI window close' is enabled? Right?
Here is some added info that may help. I do have Sp2 RC for vista installed. I will try what you said and see if that helps too.
No it stays. It Just does not show when I reboot and power up the computer.
Quote from: parkd1 on March 12, 2009, 11:34:03 AM
No it stays. It Just does not show when I reboot and power up the computer.
Ok, thanks. I am going to work again on this issue right now. My goal will be to fix it today.
Interesting. It only occurring at startup is a good clue to the cause. A few more questions while I have you here, to try to reproduce the behavior. I am testing in Vista /w SP2 RC2 right now, attempting to see it occur. Don't worry with trying that /tray parameter suggestion I made, I have already tried it.
1. Have you disabled UAC, or is it still active?
1a. If so, are you running Process Lasso with HIGHEST rights or NORMAL rights (show all user processes, or not)?
2. Are there any other users logged into the system?
3. Do you have any special third-party software you might think may be relevant (just guessing, anything unusual)? Something that also starts at login?
4. Does explorer tend to crash on your system, even rarely?
5. Does this not happen every restart? You seemed to suggest it didn't before.. I'm unsure?
6. Do you now if it also happens if you simply logoff and log back in, instead of full restarts? (I'd imagine logoff/logon is the same)
7. Are there any error events in your system application event log?
Thanks!
Btw, my current theories are these:
1. Explorer.exe is silently crashing and restarting (does the taskbar disappear briefly by chance?) at a point in the Process Lasso startup process that prevents it from recreating its system tray icon.
2. Something other software is blocking automatic startup of Process Lasso (i.e. an anti-malware application like Windows Defender). But, if something is interfering should let you know about this interference.
3. Process Lasso is crashing, but if this happened you should have seen a crash message.
The only way I've reproduced this is when Windows Defender blocks it at startup because Process Lasso is configured with highest rights. I assumed this wasn't what the report was about, but I guess I should ask if there is any possibility this is what is happening?
Hmmmmm. I have all set to below normal on start up. UAC is disabled. No other user are logged on. I am the only one. There are no errors at startup. Far as I know explorer.exe is not silently crashing and restarting. It seems to not do this all the time what makes this hard to know what is the cause at startup.
Are you using 32 or 64 bit Vista?
I am using 32. I get WdiServiceHost and WdiSystemHost service hang at startup.
Do you have an ATI video card? I've seen this attributed to bad ATI drivers. Please download and install the latest drivers/control center if you do.
No, I do not have a ATI card. Mine is NVIDIA GeForce 8800 GTS.
The gist of the article was make sure you have the latest video driver as they have seen issues between those services and video drivers.
Or you can install Vista SP3 (Windows 7) ::)
I have the latest driver installed. I keep all my drivers updated. I plan on moving to windows 7 when it comes out.
May I suggest you start investigating Windows 7 when the release canidate is released in early April?
I've been running it as my primary OS for a few months now and I love it. It is waaaaaay better than Vista. All my Vista drivers work and I haven't run into any compatibility issues with my applications. Right now I'm running build 7057 which is a build or two away from RC1.
What is way cool. Can not wait.
What version will the RC be of windows 7? I am running Vista Ultimate. Will I be able to upgrade to RC or have to wait for final?
I don't know what build number the RC will be. I would imagine maybe 7060 or higher.
You can upgrade from Vista to Windows 7 RC Ultimate. Then when Windows 7 final is released you can upgrade from the RC. I've been upgrading Windows 7 builds from Vista Ultimate.
How is it going on this one?
Quote from: parkd1 on March 22, 2009, 10:41:13 AM
How is it going on this one?
Honestly, I still don't have any answers ;(. I haven't reproduced it in any of my test beds, nor do I have any particularly good theories on how it would occur. I also don't know if the problem is specific to your system, or one many users see.
There is still the possibility that I'll stumble upon the cause, but at this point I am in desperate need of additional clues. I encourage you to continue investigating there, and see if you discover any clues that might be helpful.
I am sorry I haven't been able to resolve this for you. It isn't for a lack of effort, it is simply that I have no answers at this point ;(.
That's ok. All we can is keep an eye on it. Maybe someone else will have this too and be able to help. Not really a big deal. I just kill and restart and all is good. Maybe SP2 will help or windows 7 just have to wait and see.
I have also experienced this on my system intermittently (WinXP Home SP3). I have PL configured to load at user login and only have myself as Admin as the sole user on the system. Usually all I have to do is log off and log back on to fix it. Typically it happens after a restart or shutdown/reboot. I assume it is just a timing issue. I had asked when I first started viewing the forum if PL could be made to be one of the first processes started upon bootup so that other processes could benefit from it's function. I still want it to start as early as possible, but I wonder if it needs to delay start up just a tad or maybe wait for specific processes to start before it does to work properly?
Hmm..interesting. It does sound like some sort of timing issue... or at least the timing is what causes the errata to manifest. I don't reboot or logoff or restart much, so perhaps that is why I've never seen it. My test beds are bare bones, so perhaps they aren't as affected (or maybe I haven't done enough logging off or restarts).
I can try playing with the start order, or delaying initialization a little while. However, I'd rather know the cause before I try work-arounds.
While working on PL v3.61.1 beta, I think I've finally discovered the possible cause of this problem. Its manifestation depends on timing and specific system conditions (and other software installed), so it makes a lot of sense. I make a fix in v3.61.1, then back-port it to the last final build if all goes well.
I am pretty sure errata could have possible manifested under certain conditions, so I'm throwing out a quick update to the last final, v3.60.7. This update will include this fix. Let us hope it is the fix those who've seen this issue have been waiting for ;).
The new beta version won't have this fix until v3.61.1. I hope to have that version released in a few hours, though I still have a good bit more work to do.
Thanks will give it a try and see if it fixes the bug.
Grrrrr that did not fix it.
Ok, thanks for testing. Maybe I'll come across some other possibility as there may be similar bugs lurking around. I will keep you updated.
I have a Dell Inspiron 1545 Core 2 Duo Laptop with 4G RAM and Windows 7 X64. The PL icon was disappearing at startup about 50% of the time. The final fix that made this work was to access the Task Scheduler entries for startup @ login. I found the default entries for both the Governor and the GUI were both set to not start when on battery power. I unchecked these as i want them to start no matter what. The other change i made was to add the /recovertrayicon switch to the command line. I got this from the extra recover tray Icon exe that you included in the start menu options...but i removed the /showwindow switch since this is actually not necessary or even desired. This seems to have fixed the problem 100% of the time. I write this here in case anyone else has this problem. This is the ultimate fix. Maybe Jeremy can work out another way, but this works for now. ;D
Thank you Hotrod, that is very helpful! It may allow me to finally track down the true cause.
Ironically, the switch (and subsequent behavior) you request to be removed is something other people have been pressuring me to remove anyway -- and I promised to do. So, I will go ahead and do that in the next build.
So, for now, at least we'll apparently have a work-around --- which I'll take in the absence of a definitive known cause. I tried again to address this in v4.00.06 RC1, but apparently failed ;(. It seems to be influenced by startup timing.
I think I finally found the true cause ;). I was on the right path, but missed a part. That last clue finally did it for me ;). Thanks!
It was, as I long suspected, a race condition on the main window creation and system tray window creation. I now have a proper event so any other thread needing that main window won't try anything until the main window is fully initialized.
Not sure where this fits in, but I have the exact opposite issue now. I can't say in what beta build this cropped up in, but it was very recently. I'm now running 4.00.15 and I can't get the main window to appear normally when launched.
That is, when I run ProcessLasso.exe, it goes right to the tray, and I have to restore it from there to show the window. It doesn't matter if I use the /showwindow switch, the /tray switch, or none at all.
I don't have "Close window to system tray" enabled.
Is there a way to run ProcessLasso.exe and have the window shown right away?
Quote from: Scott on November 15, 2010, 09:44:08 PM
Is there a way to run ProcessLasso.exe and have the window shown right away?
I modified it so that it always hid, at the request of a couple users. This seemed to be the desirable behavior, and standard behavior of resident applications that start to the system tray. The /showwindow parameter seems to not work as a result.
I will add a new parameter to facilitate this, or fix the existing one.
Thanks