Author Topic: unable to disable logging in Process Lasso 6.8.0.4 (Read 9809 times)

anthropos · « **on:** June 10, 2014, 10:26:31 AM »

Greetings!

I just noticed that - for my machines (Win 8.1 Update in 32 and 64 bit) - the option to disable the action log is no longer working; Process Lasso still logs everything it does. I disabled it recently to further save the battery life on my tablet even by the merest means and after the last update I am no longer able to do so. No reset and reconfiguration prevents Process Lasso from writing the action log.

BenYeeHua · « **Reply #1 on:** June 10, 2014, 11:05:06 AM »

WFM, I untick the "Logging enabled" and it stop logging anything(even after restarted Process Lasso), so I guess it is something only happen with your computer setup.
If there are other people facing the same issues, please reply at here to let me know, so it is more easy to find out why it happen.

---
BTW, you can power save more by not running Process Lasso GUI, and also slowing down the Refresh internal.

anthropos · « **Reply #2 on:** June 10, 2014, 11:11:28 AM »

Maybe something went wrong during the update as the logging option were already disabled. I simply deinstall Process Lasso and reinstall it again. Like I said, this happened on three different machines and the only same thing is that they updated PL and had their action log already disabled.

And thank you for the further tips, the battery life is the only strength of an Iconia W510.

anthropos · « **Reply #3 on:** June 10, 2014, 11:46:53 AM »

Sadly, this behaviour continues even after de-installing, restarting and reinstalling Process Lasso. I disabled every option related to logging and PL begins to log shortly afterwards every time. O well, I hope this vanishes as fast it appeared.

edkiefer · « **Reply #4 on:** June 10, 2014, 01:17:31 PM »

disabling log seems to work here fine (latest version) .

BenYeeHua · « **Reply #5 on:** June 10, 2014, 03:44:26 PM »

Quote from: anthropos on June 10, 2014, 11:11:28 AM

And thank you for the further tips, the battery life is the only strength of an Iconia W510.

Yup, Atom is worst now, but it will be better after a few years, as Intel has change the research rate of Atom to more faster, for getting mobile market.
---
I just tested for disabled the log for 5 mins, and it is still disabled.

Maybe you can try list the dll that loaded into Process Lasso+Governor(as I don't know who is managing the log.

) and post at here, it can be some other software that causing this issues.

Quote

You can download this software, extract it, on the extracted folder, holding shift and right click, click on "Open Command Windows here", then run this command.
Code: [Select]
listdlls -v processlasso.exe >pldll.txt
Code: [Select]
listdlls -v processgovernor.exe >pgdll.txtAnd also click accept the EULA, if you are just a normal user.

Then the extracted folder should be having pldll.txt and pgddl.txt, and it will contain all dll info that loaded into processlasso.exe, and you can post it on here by Attach it.

offchu · « **Reply #6 on:** June 10, 2014, 08:49:48 PM »

Same problem here. Also "Disable CPU Core Parking during ProBalance restraint" selection won't persist.

Win 7 x64

BenYeeHua · « **Reply #7 on:** June 11, 2014, 09:29:33 AM »

Thank for the dll list, so far I found a few point, and I need the OP reply too to confirm the similar point.

1.Did both of your Windows Language is not English?
Based on the dll list, there are some corrupt, which showing it is not English.
This might be the reason why it don't works.

2.Both of you are not using the same anti-virus, Comodo, right?

3.I found 2 dll has been inject into Process Lasso(not Process Governor).
a.DisplayFusion
b.Raptr
I guess this should not affecting this function, as both of them are for UI.

anthropos · « **Reply #8 on:** June 11, 2014, 10:40:23 AM »

I will do it too and update this post then.
Until then, I am not using Comodo just Windows Defender; and all my Windows versions are German ones with German Display Language on two machines and on one machine with English Display Language. Process Lasso works two times in English and two times in German.

I now got the first list from my tablet; the other machine is busy making a full backup and I will redo this on it when it is ready again.

BenYeeHua · « **Reply #9 on:** June 11, 2014, 06:30:58 PM »

Quote

Until then, I am not using Comodo just Windows Defender; and all my Windows versions are German ones with German Display Language on two machines and on one machine with English Display Language. Process Lasso works two times in English and two times in German.

So, all are coming with German, when you buy it?
Because just changing the display language don't change the system itself is having difference locale language.

edkiefer · « **Reply #10 on:** June 11, 2014, 07:52:05 PM »

There does seem to be a bug here , I left log disabled all day, and noticed some logging is being writen , the "Probalance restraint ended" action seems to show, but not otheres, like power config or game, or lower priority .

BenYeeHua · « **Reply #11 on:** June 12, 2014, 06:34:53 AM »

Yup, there should be a bug for the beta that changed/updated the log system, as my log is clean up after update to it.

Quote

6.8.0.4 Fix GUI Fix slow app init in recent builds due to large log files

edkiefer · « **Reply #12 on:** June 12, 2014, 07:19:00 AM »

yes, saw that but your not getting any logs with it disabled for long time ?
I am of course on latest build .

BenYeeHua · « **Reply #13 on:** June 12, 2014, 10:00:19 AM »

I do not testing for disable it for a long time yet, testing it now.

edkiefer · « **Reply #14 on:** June 12, 2014, 10:10:34 AM »

I cleared the log and disabled log and within a hr or so I get "Probalance restraint ended" logs only .
Mainly from my browser , alt-tabing it .

BenYeeHua · « **Reply #15 on:** June 12, 2014, 11:10:59 AM »

Yup, so at least the "Probalance restraint ended" log is easy to reproduce, but I wonder did the logging can't be disable(which is mostly the topic saying about) is the same bug or not.

edkiefer · « **Reply #16 on:** June 12, 2014, 11:12:40 AM »

Yes, the others need to comment whats being logged with it disabled, if there getting other logging to .

offchu · « **Reply #17 on:** June 12, 2014, 03:33:34 PM »

I only get "Probalance restraint ended" logs with logging disabled.

BenYeeHua · « **Reply #18 on:** June 12, 2014, 06:38:14 PM »

Quote from: offchu on June 12, 2014, 03:33:34 PM

I only get "Probalance restraint ended" logs with logging disabled.

Thank for the info, as least we know 3 of us is the same bug, and it is not about windows language, which is a good news I guess.

So I guess the OP is having difference bug, or just don't observe correctly?
Because he said that

Quote

Process Lasso still logs everything it does

And normally user only has Restraint log enabled, so you know.

anthropos · « **Reply #19 on:** June 15, 2014, 06:47:05 AM »

Sorry, I was away the last days and not on my other machine, so I had not the chance to upload the other dll list. Maybe the topic title and my wording are misleading as I never specified if I only see one type of events in the log or all types of events.
Till now I only see the action "ProBalance restraint ended", so I think it could be the same bug as I just checked if the log is active.

BenYeeHua · « **Reply #20 on:** June 15, 2014, 10:55:45 AM »

Thank for the info, and I think no need to upload the DLL list, as it is a bug with Process Lasso.
And thank for reporting it early, so we know it is a bug that happen after this beta.

So, this bug is about the "ProBalance restraint ended" keep logging, even logging is disabled.

anthropos · « **Reply #21 on:** June 15, 2014, 12:15:34 PM »

Glad to be of any help, although it was mostly a coincidence.

BenYeeHua · « **Reply #22 on:** June 15, 2014, 03:08:33 PM »

If you know, sometimes you need some lucks to found some hidden bugs.

Normally we just test by doing the daily use, which mostly is the default setting works or not, and most of the time, it is already tested by the dev.

Jeremy Collake · « **Reply #23 on:** July 05, 2014, 06:48:34 PM »

Thanks guys, I am working on this.

BenYeeHua is right, after years of incremental maintenance, we had a bit of feature creep happen. With all these features, the chances of any one, or combination of features, malfunctioning increases. Particularly non-default settings. This is a good example of such an error.

The good news is that it's non-critical.

News:

Author Topic: unable to disable logging in Process Lasso 6.8.0.4 (Read 9809 times)