Process Lasso Releases

Yes, I noticed when I ran the updater manually it said 235 (which was already installed), but afterward it says 237. Jeremy must be burning the midnight oil

 

I have seen this before with some CPU Balance-releases. Sometimes all executables are signed, sometimes 2-3 of them are not digitally signed.

With Process Lasso .237beta three files are not digitally signed:

But soon v9 will be released (according the the revision history):

 

Have you tried clicking on the words "Process Name" at the top of the Processes column. PL can sort processes in a variety of ways by clicking the name of the column, e,g,, CPU avg, CPU Time, etc as well as by Process Name both ascending and descending.

 

.237beta was yesterday, .239beta is out
All executables are now digitally signed.

 

Same thing today except the update didn't continue. I had to restart PL and check for updates again.

 

Yes, done all that. I have stopped using it as I noticed it was affecting Chrome page load times by adding a second or more. I used this to measure, https://chrome.google.com/webstore/...ig?utm_source=chrome-app-launcher-info-dialog.

 

Did you confirm that PL was the cause of the delay by checking the lower
half of the PL GUI to see if any process related to Chrome was being restrained?

Sounds strange.

 

Process Lasso 9.0.0.241 beta is out

 

Process Lasso the quick change artist. ...Never out of beta. I have to check to see if it is available. I got 9.0.0.237 last night.

 

I got it....

 

PL is updated .245 (for) now.

 

PL has updated to .249.

 

It's .251 beta build now.

 

PL just updated to .257 here.

 

Thanks! Updating now...

Just for information to all, I've been in touch with Jeremy via email to address possible process handle "leaks" generated by the Process Governor (in v8 and v9 Beta). Although he would say that this happens rarely and will not cause noticeable performance and incompatibility issues for most users, Jeremy still chose to fix those occurring leaks.

He confirmed to me that his "fixes" are being shipped in the beta, starting build .247. The "fixes" are still experimental, though, meaning that they are implemented, but the leaks may still happen, and therefore they may not be the right fixes. He said it's difficult to detect this bug due to the rarity of it happening. Jeremy is still finding the right fix.

 

Yep, 257 just hit my machine as well

 

.259 is up.

 

I had an error updating so I had to manually update.

Edit: I had the same error on all three of my machines.

 

I didn't encounter any error when I updated it. Maybe, there's a server issue when you updated.

 

+1

 

Me too @Krusty , going to have to manually update myself, I will note it
to alert JC.

 

What made mine different? I really didn't encounter that error. Good for me, then.

 

Maybe this is the reason: https://bitsum.com/company-news/the-week-of-fire/

 

Yeah I read that, I just want to make sure that covers Error #4
JC gets ahead of himself sometimes, he burns the candle at both ends.
I don't see how he or Dan for that matter do it. All I can guess is they
are passionate and driven, not a bad thing I guess.

 

A new beta is on the way: .263