9.0.0.318 is available v9.0.0.318 – April 27, 2017 Fixed issue with switching between profiles would cause governor to refuse to acknowledge changes until it restarted Fixed issue with creation of new profiles when selecting to use current config Fixed some new features of the silent/unattended install Fixed an issue with the new, now optional, file-system backed synchronization (used for UNC paths and those who have thousands of remote instances) Fixed issue where when there was contention for the configuration, it could become locked in a static state until the governor (or GUI) was restarted – either could have manifested this Replace a file-system lock with mutex, returning to prior behavior while giving those who need a file-system lock access to one. Restart Process Lasso after changes in ‘Reconfigure the way Process Lasso starts’ Increase efficiency of file-system lock by approx 50% – though this is now something not used by most (must be manually enabled) Remove old warning about changing settings when the ‘reset to defaults’ section is checked in the installer Added slight delay to governor when a config change is detected to deal with rapid-fire changes like sliders Improve config profile management, creation, and deletion Improve config import/export Re-enabled creation of config profiles (were disabled while under maintenance for safety) Other minor code adjustments and improvements Updated French and Russian
Very impressed with 318. resource usage and responseiveness are very solid. JC hit this one out of the park imho
It never stops .321 beta Released ("If you are using default memory priorities on processes, you should update to this build immediately.")
Possibly. It could be my imagination but PL does seem 'quieter' with this build, maybe because of the default memory priorities on processes fix.
The changelog for the beta was removed from the website Perhaps a new build which includes the fix is coming very soon I agree ---------- Edit: .325 beta released (04/30/17)
My old Core 2 Duo loves this software. I'm still tossing up between Process Lasso or to just use CPUBalance if only to reduce overhead.
Given it's an older C2Duo CPUBalance would be sufficient and keep memory usage to a minimum. But either way your right, this software is amazing for older systems.
Guys, Jeremy said through email that he's developing a new engine (a rewrite of the "core engine") to be used by his new products. What could these new products be? He said he needs to update/upgrade his 15+ years old engine. During the development of the new engine, he's sure that he can pinpoint the problem about process handle leaks of PL v9 and v8. So, the bug might be fixed as the new engine is developed.
Yeah, this has been on his mind, not the first time he has hinted at something like this while still being guarded and cryptic at the same time. You can bet that whatever he comes up with will be well worth his time and ours
.329beta Released (05/03/17) Edit: .331beta (05/04/17) Edit 2: .333beta (05/05/17) Edit 3: .335beta (05/06/17) Edit 4: .337beta (05/09/17)
Process Lasso v9.0.0.340 available via internal updater (apparently not a beta) This is a minor release to correct some deficiencies in recent builds and completes early maintenance on the CPUEater app, which was only quickly addressed prior to the last scheduled update. The core problem with prior use in v9 was the ‘Ignore children of foreground processes‘ setting, which was not properly turned off prior to starting the test (at least not turned off and the governor given time to update it’s settings!). Upon reflection, this default was changed, and the CPUEater was rewritten to give warning in case of this option, which simply means you have to click away from the CPUEater window before ProBalance will kick in. However, once a system is inundated, this may be hard! REMEMBER, the CPUEater *only* creates normal priority threads in normal priority class processes, thus this sort of monopolization even blocking higher priority threads should not be possible, but it is! This is the core CPU Scheduler deficiency that ProBalance corrects. Show CPUEater options by default Remove ‘Ignore children of foreground processes’ checkbox from CPUEater, as it could not be updated reliably from there Change default setting of ‘Ignore children of foreground processes’ to false, as this may be the preferred configuration for most (it is for me). If you see it act on anything you don’t want, exclude that specific process. Remove some experimental code in prior builds Improve uninstaller temp path use so that it functions better (requires a product reinstall to replace the uninstall.exe file) Update French
On a Win7 x86 machine and Process Lasso. This machine always stays in shadow mode permanently. Do I need to make folder/registry exceptions in SD for Lasso to keep some ever changing files for a correct functioning?
Latest (I think beta, 341?) failed on two machines, some sort of sxs error. Manually downloaded and installed latest stable 340. Back to normal.
I have tried the beta-download links, and beta 345 is now available. It seems to be fresh, it twas timestamped some hours ago.
Last thing I decided to do before shutting down was check to see if there was an update to PL, and there was. But it failed with this error. Then this morning at boot, PL didn't load, so I tried to manually start, and then I got another error. I will have to get the latest beta from the Bitsum website.
