Bitsum Community Forum

General Category => Process Lasso => Topic started by: DeadHead on November 12, 2014, 03:16:56 PM

Title: Energy saving options bug
Post by: DeadHead on November 12, 2014, 03:16:56 PM
I think I might have reported this before.

It seems that when I enable the energy saving feature, it will bug out when switching to another user, and gets stuck in energy saving mode, never reverting to high performance. I have no other software installed that interferes with the power plans.

So, something's up when it comes to several accounts on the same computer, at least that's what it seems like.
Title: Re: Energy saving options bug
Post by: Jeremy Collake on December 12, 2014, 11:11:57 PM
Thanks for the report, and sorry for the late response. This scenario wasn't handled well. I need to do some research, so it may be few builds, but is on my agenda now.
Title: Re: Energy saving options bug
Post by: DeadHead on December 13, 2014, 07:10:12 AM
Not easily reproduced, I haven't actually stumbled on this issue for the last couple of weeks, so not really sure what's up. I'll let you know if I see it occur again.
Title: Re: Energy saving options bug
Post by: edkiefer on December 19, 2014, 10:04:08 AM
This is little OT, but power plans with 7.4 still seem to get confused between game bitsum HP and power app plans, as I have calc.exe setup as just test bed for HP plan.
I use it daily and now today PL shows my plan in HP but calc hasn't been used today , fresh boot .

So somewhere, I have not pinned down cause but it getting confused .
Title: Re: Energy saving options bug
Post by: Jeremy Collake on December 19, 2014, 10:10:47 AM
Was Calc running when you did a manual update to 7.4? If so, that is the cause.. a bug now fixed. It doesn't affect many, as it won't do an auto update in gaming mode. Otherwise, something else could have happened. Please continue to report.+




Title: Re: Energy saving options bug
Post by: edkiefer on December 19, 2014, 11:53:15 AM
I don't know, maybe though, as I use it on an off during day .

Ok, look at log , you can see calc.exe was not running AFAIK , but processgovernor at 17:48 changed it to HP .

http://i.imgur.com/vSAgNG8.jpg (http://i.imgur.com/vSAgNG8.jpg)

To me it looks like I had calc.exe running, I started BF4 and while it was loading (it starts off webbrowser ) I closed calc.exe before final entering game .I don't know what triggered that 12:17:48 PID 2740 processgovernor active powerplan change to HP .
Title: Re: Energy saving options bug
Post by: Jeremy Collake on December 19, 2014, 11:58:01 AM
Ok, thanks. Let me spend some time thinking about this scenario.
Title: Re: Energy saving options bug
Post by: edkiefer on December 19, 2014, 12:10:41 PM
ok, recreated it .
here what happens .
default power plan = my custom power plan .
run calc.exe =power plan HP
start BF4 =power plan bitsum HP
close calc.exe= my custom power plan change , while BF4 is running(seems wrong)
enter game and exit = power plan HP now .
Title: Re: Energy saving options bug
Post by: Jeremy Collake on December 19, 2014, 12:42:21 PM
Ah, yes, I see clearly now. Thank you for taking the time to figure out the sequencing.

I'll work on better handling when multiple power automation rules are in-effect simultaneously - it's been on the agenda for a while.
Title: Re: Energy saving options bug
Post by: edkiefer on December 19, 2014, 12:59:48 PM
I still think it would be good idea to have a default x power plan saved .
So when PL starts or does a check, if no rules are in place, make sure xx plan is used .

this would be a safegaurd type of thing, so the default keeps right over time .
Title: Re: Energy saving options bug
Post by: Jeremy Collake on December 19, 2014, 01:09:29 PM
I completely agree, and it *is* coming for sure. Already been in the works. I just have to do all this right, not just hack it in. A lot of code is being refactored as I type ;).
Title: Re: Energy saving options bug
Post by: edkiefer on December 19, 2014, 02:24:11 PM
Quote from: Jeremy Collake on December 19, 2014, 01:09:29 PM
I completely agree, and it *is* coming for sure. Already been in the works. I just have to do all this right, not just hack it in. A lot of code is being refactored as I type ;).
Cool, got it .