Process Lasso v6.0.3.23 beta config eaten

[bertie97]

Just an FYI.
I've just realized that updating to Process Lasso v6.0.3.23 beta killed my config.
All my game processes etc went & the power saver settings, no sleep etc all disappeared. 
Conclusion - ini eaten 

I found that re-entering the power savings took 2 tries before they stuck.  Coincidence/user error?
Seems allow display but not PC to sleep isn't working.
Did I see a request for a right click function on the above setting?  If not, I think it might be useful to have one when selecting active processes in the GUI.

Should have backed up my ini more recently    not as if I didn't know it was a beta! 

I noticed when backing the ini up just now that if an ini already exists the save process doesn't warn about an overwrite.  This might occasionally be a problem for some users, especially as the default write location is the install dir...

[BenYeeHua]

Ya, and luckily it is just a beta, just think about what will happen if it is stable version.

[edkiefer]

I the config ini should be backed up in the default path C:\Users\Ed\AppData\Roaming\ProcessLasso\config

One being used right now is in C:\Users\Ed\AppData\Roaming\ProcessLasso . It was copied over when the beta updated .

That said some features are not working right now, at least for me like power profiles .

[bertie97]

When I export it goes to ..AppData\Roaming\ProcessLasso

Just found none of my prevent sleep functions are working.   

"Looks like I picked the wrong week to stop sniffing glue..."   - Airplane 

[Jeremy Collake]

Yes, this is something I've noticed and will be resolving. Much work still remains in this rather large update.

[bertie97]

Rolled back to Process Lasso v6.0.3.4 & I find my CPU core parking dialog won't hold settings anymore (again)     
Not done a clean uninstall/install yet tho - just fiddling 

[BenYeeHua]

Rolled back to Process Lasso v6.0.3.4 & I find my CPU core parking dialog won't hold settings anymore (again)     
Not done a clean uninstall/install yet tho - just fiddling 

It might be using a older version of Park-control, try download the newest version from here.
http://bitsum.com/about_cpu_core_parking.php
---OT line
And the link at the "Looking for?" is using the old one.
Which is http://bitsum.com/other/about_cpu_core_parking.php

[Jeremy Collake]

Rolled back to Process Lasso v6.0.3.4 & I find my CPU core parking dialog won't hold settings anymore (again)     
Not done a clean uninstall/install yet tho - just fiddling 

Yes, as BenYeeHua says, that is the old, unfixed version of ParkControl. While you patiently wait for me to finish the beta and make it final, again as BenYeeHua says, use the stand-alone version of ParkControl, if you have to.

[bertie97]

Yes, that is the old, unfixed version of ParkControl. While you patiently wait for me to finish the beta and make it final, use the stand-alone version of ParkControl, if you have to. Once you set the parking settings, most people don't change them again regularly (that's what power profiles are for).

OK I can take the hint   

I had assumed it was a reversion to the old PC but hadn't had time to cross check the version numbers.  Decided to pad out the thread with useless whining instead.

[Jeremy Collake]

lol, I'm really criticizing myself here. I could/should have more done by now. I do what I can I suppose. It won't be long now, I don't think. Some barriers to productivity the last week have been dealt with and I'm moving forward again.

[bertie97]

I'm now on the new beta .25b (thanks for pushing it out) & things are looking a lot better.

I did wonder about the number of threads shown in the GUI.  I don't normally full-screen the GUI but just after boot today I did & found that whilst 73 process threads were running only about 18 were shown.  (If windowed I would have to scroll down a little to see all the 18-20 entries so hadn't actually counted them previously.  No 50" monitor yet  )
I seem to recall using PL to track svchost instances in the past but they aren't displayed now.

Is this an intentional pruning whose introduction has slipped past me?

[edkiefer]

Make sure you have "manage processes of all users" enabled in main menu .

[bertie97]

Thanks edkiefer, somehow that had switched to an unticked state.
So familiar with it being active I hadn't even thought of that switch... 

[BenYeeHua]

Thanks edkiefer, somehow that had switched to an unticked state.
So familiar with it being active I hadn't even thought of that switch... 

That's normal, as we has been asked to set this setting for the first time we start Process Lasso.

[edkiefer]

That's normal, as we has been asked to set this setting for the first time we start Process Lasso.

Right,  after you run through installer you get to startup options, in there you get option to set this .

[Jeremy Collake]

I'm evaluating, resolving, and testing the configuration file migration now, btw.. I'm shooting for a new beta build later today. The existing configuration should never be lost, it will remain in its original path (%APPDATA%\ProcessLasso\prolasso.ini). The new one is in the 'config' subfolder at the same location.

I really can't express how invaluable your (all of you, plus a few more) contributions have been. As you know, there is no staff here other than myself, so your testing and bug reports really make a huge difference.

[bertie97]

I normally see all the process activities so I guess when my config went that setting went too.  Having not usually had to search for the switch in the menus it has slipped past me on this occasion. 
I usually check the Make Process Lasso your System Overlord with absolute powers of life & death over all users box on install...

@ Support - Good to know that my/our gripes are useful on occasion 

[BenYeeHua]

@ Support - Good to know that my/our gripes are useful on occasion 

Yes, and this is good, if any product has many weakness, and you don't gripes for that.
Then devs will not know about that, until devs found the weakness and improve/fix it.

[Jeremy Collake]

I'm delayed a bit, which is no real surprise to anyone who knows me. After initially re-factoring the inter-process communication between instance(s) of the governor and instance(s) of the GUI, I decided to just rip that old system out. I never liked it, it's excessively complex. The new system relies on the log to pass most information, except for simple events.

@BenYeeHua: This change will fix the graph tooltip discrepancy that you noted a while back, among other things.

The log entries themselves are being better type defined to facilitate this. It is taking some time to properly define all log entry types and change the code round. Tedious, tedious work since there are so many log types. But, it won't be long.

[BenYeeHua]

@BenYeeHua: This change will fix the graph tooltip discrepancy that you noted a while back, among other things.

Great.
Remember to put a old "vs" new screenshot/picture, as it is more understandable.(as I forgot about what's issue is that. )

[Jeremy Collake]

I'll show you. This is version is turning into a monumental chore, though it's needed. The end result of this beta series will be a new major version.

[bertie97]

This sounds like an interesting development.  Looking forward to trying it...
Even if it does eat my config!

(But really, I know this is unlikely given the mod mentioned above  )

[BenYeeHua]

This sounds like an interesting development.  Looking forward to trying it...
Even if it does eat my config!

(But really, I know this is unlikely given the mod mentioned above  )

So, did you has started backup the config file?

[hanemach_gt]

So, did you has started backup the config file?

I would not like to advertise myself here, but I use my own solution for Process Lasso INI backup: https://bitsum.com/forum/index.php/topic,3114.0.html

[BenYeeHua]

I would not like to advertise myself here, but I use my own solution for Process Lasso INI backup: https://bitsum.com/forum/index.php/topic,3114.0.html

My config don't change too much(I only enable "manage all processes" for now), backup the config everyday might be useless for me.

[gman68w]

I think there's something wrong with the way PL is reading the config settings, or with where it's trying to load them from. It's not saving my settings on exit, or if it hasn't reset them entirely from the last update, it isn't reading the config file properly.

[edkiefer]

Yes, it has issues with saving .
Last few beta have many changes under the hood and may take some beta's to get there, give it some time .

[Jeremy Collake]

As the code is finalized and regression tested, there may be cases where the configuration file is lost, especially in beta->beta updates. By the final, the migration from the previous final build will be guaranteed. I recommend you export your configuration file if you need to make sure it's preserved. You can then re-import it. The paths used are shown in the About box, so you can check there to see if they have been set anomalously.

[bertie97]

@BYH - yep I did ensure I had a config backup this time   

@hanemach_gt - I did just try your script, looks like you covered a few bases there.  I liked the prefix # that could be really helpful when I'm messing about. 

[BenYeeHua]

@BYH - yep I did ensure I had a config backup this time   

Good.
I don't see any reason for not being backup a small important config file everyday, except you don't touch it too much, just like me.

[Jeremy Collake]

I am looking at this problem in a test bed, so will be sure it is resolved here shortly. The symptoms are that no configuration changes are saved.

I am merging this issue with a similar thread regarding the loss or inefficacy of the configuration file in the new beta.

[Jeremy Collake]

What is actually happening in the current beta is that the configuration file is being reset when Process Lasso is restarted (on some systems where an upgrade was performed). It should work properly in v6.0.4.3 beta.

[BenYeeHua]

What is actually happening in the current beta is that the configuration file is being reset when Process Lasso is restarted (on some systems where an upgrade was performed). It should work properly in v6.0.4.3 beta.

Will test for it after you push that version.

[bertie97]

The 6.4.0.1b did eat my config during the auto-upgrade today ....but I had a backup ready 

[Jeremy Collake]

That build will most likely keep eating it. The migration was broke under some installs, such that it would constantly kill your configuration file when it restarts.

v6.4.0.3 should do better. It's uploading now.

[edkiefer]

6.4.0.3 seems to be working better . It is saving ini in the config folder .
I am having issue with log setting on power profiles from sticking (its off default, all other logs on)

Edit : the power profiles don't seem to switch either . I don't see the line in the ini to to edit .

[BenYeeHua]

Using v6.4.0.3 beta now.
And I found every start of Process Lasso, the Actions Log will showing Action:action 0x3b, which showing More info:Managing processes for user(s):All users.
----
And did you tweak a bit the default setting?
I saw a windows jump up and asking me to restore to ProBalance default, or this is caused by the unsaved config?

[edkiefer]

Using v6.4.0.3 beta now.
And I found every start of Process Lasso, the Actions Log will showing Action:action 0x3b, which showing More info:Managing processes for user(s):All users.
----
And did you tweak a bit the default setting?
I saw a windows jump up and asking me to restore to ProBalance default, or this is caused by the unsaved config?

yes, that shows in log when you change managing user in main . think its new log entree that shows on startup

[Jeremy Collake]

I am having issue with log setting on power profiles from sticking (its off default, all other logs on)

Yes, I see the problem with 'Log application power profile change events'. I will correct that. Thanks!

Edit : the power profiles don't seem to switch either . I don't see the line in the ini to to edit .

The application power profiles?

[Jeremy Collake]

Using v6.4.0.3 beta now.
And I found every start of Process Lasso, the Actions Log will showing Action:action 0x3b, which showing More info:Managing processes for user(s):All users.

That just means there is no string for that action yet. I am slowly adding them, and will disable any that don't have an associated string by final.

I saw a windows jump up and asking me to restore to ProBalance default, or this is caused by the unsaved config?

It's a leftover from an old change to some defaults. I'm going to kill it, thanks for reminding me!

Thanks!

[edkiefer]

Yes, I see the problem with 'Log application power profile change events'. I will correct that. Thanks!

The application power profiles?

yes app power profile switching . I tested with my default power profile and run game I have it enabled (high performance) and alt-tab and checked no change .

Edit: not sure if this is wrong or right but when I use option , right click on action window "jump to log file on disk" It opens a new explorer process (so you get 2 explorer.exe running) . Closing the folder does bring count back down .
If I open folders normal way 1 explorer can handle all of them  .

[BenYeeHua]

It's a leftover from an old change to some defaults. I'm going to kill it, thanks for reminding me!

Thanks!

This show that, every detail is important to report, it don't care it is less or more important.

Edit: not sure if this is wrong or right but when I use option , right click on action window "jump to log file on disk" It opens a new explorer process (so you get 2 explorer.exe running) . Closing the folder does bring count back down .
If I open folders normal way 1 explorer can handle all of them  .

It might be windows used for prevent crash, if it launch by other process instead of Explorer.exe?
As I has "Folder options-Launch folder windows in a separate process" ticked, this is normal for me.

[edkiefer]

This show that, every detail is important to report, it don't care it is less or more important. ;)It might be windows used for prevent crash, if it launch by other process instead of Explorer.exe?
As I has "Folder options-Launch folder windows in a separate process" ticked, this is normal for me.

I just checked ,that option is not enabled "Launch folder windows in a separate process"
Like I said if I open multiple folders from my computer I see only 1 explorer process for all folders open .

Its not big deal, I guess he coded it with that flag on .

[BenYeeHua]

I just checked ,that option is not enabled "Launch folder windows in a separate process"
Like I said if I open multiple folders from my computer I see only 1 explorer process for all folders open .

Its not big deal, I guess he coded it with that flag on .

I think you can try tick/enable it, if you open a folder with many picture/video and scroll with fast speed/one of the video has high bitrate, it(explorer.exe) might be crash by the thumbnailer.

[edkiefer]

I rather not have multiple processes . I just tried scrolling though my raw images in picture folder, no slow downs or anything .
Maybe if I had all pics in one folder but I have it set it makes a timestamp folder when I DL from camera to picture folder .

[BenYeeHua]

OT

Ya, the issues that I facing with Explorer.exe is, the IE has some malware active-x or other thing.
When I open My Computer, it will crash because of that, and I fixed it by running IE(No add-on) and reset it.

And when I open a folder with a high bitrate video, it hang because it want to thumbnail that video, which using maybe one core for that.
----
I just thinking that, what is the difference with "Launch folder windows in a separate process", did it reduce leak just like Chrome?
Or it just want to prevent some crash for the main Explorer.exe?

[edkiefer]

not sure , I guess it can add some stability having more explorer exe run for each folder .
The downside would be added resources used maybe .

[BenYeeHua]

not sure , I guess it can add some stability having more explorer exe run for each folder .
The downside would be added resources used maybe .

I think yes.
From the Help.

Increase the stability of Windows by opening every folder in a separate part of memory. (Use this setting if your PC frequently stops working and you want to minimize or troubleshoot problems. Choosing this setting might slow down your PC.)

It might slow down your PC while the Ram is almost full.

[Jeremy Collake]

Edit: not sure if this is wrong or right but when I use option , right click on action window "jump to log file on disk" It opens a new explorer process (so you get 2 explorer.exe running) . Closing the folder does bring count back down .
If I open folders normal way 1 explorer can handle all of them  .

That's right, it's a secondary explorer instance. This really isn't a large waste of resources since they share so much of their virtual memory, and regardless is the preferred way to launch the folder view for the time being.

[Jeremy Collake]

yes app power profile switching . I tested with my default power profile and run game I have it enabled (high performance) and alt-tab and checked no change .

Is it possible that this was simply a side effect of the failed configuration file? It appears to be working, now at least. I'll issue a new build some time in the next few hours.