[1.0.2.x] Issue purging SBL with exclusion list

[vmech]

After starting a process from ISLC exclusion list, followed by termination of this process, ISLC stops regular purging of standby lists until the Start/Stop is pressed, or ISLC is restarted.

[Wagnard]

After starting a process from ISLC exclusion list, followed by termination of this process, ISLC stops regular purging of standby lists until the Start/Stop is pressed, or ISLC is restarted.

Hi, thanks for the report, I will investigate.

[Wagnard]

After starting a process from ISLC exclusion list, followed by termination of this process, ISLC stops regular purging of standby lists until the Start/Stop is pressed, or ISLC is restarted.

Should be fixed with 1.0.2.7

[vmech]

After starting a process from ISLC exclusion list, followed by termination of this process, ISLC stops regular purging of standby lists until the Start/Stop is pressed, or ISLC is restarted.

Should be fixed with 1.0.2.7

Thanks, now exclusion list is working as expected.

[vmech]

After starting a process from ISLC exclusion list, followed by termination of this process, ISLC stops regular purging of standby lists until the Start/Stop is pressed, or ISLC is restarted.

Should be fixed with 1.0.2.7

Thanks, now exclusion list is working as expected.

Nope. Not fixed fully



PS. The screenshot state was preceded by multiple launches during the day of application from exclusion list, with long periods of use (several hours in a row).

[Wagnard]

Should be fixed with 1.0.2.7

Thanks, now exclusion list is working as expected.

Nope. Not fixed fully



PS. The screenshot state was preceded by multiple launches during the day of application from exclusion list, with long periods of use (several hours in a row).

At the time of the screeshot, no application in the exclusion list was running? You must be 100% certain that there were no process active

[vmech]

Thanks, now exclusion list is working as expected.

Nope. Not fixed fully



PS. The screenshot state was preceded by multiple launches during the day of application from exclusion list, with long periods of use (several hours in a row).

At the time of the screeshot, no application in the exclusion list was running? You must be 100% certain that there were no process active

No, application didn't start, and it didn't freeze in processes. The purity of the experiment is observed (I myself was surprised by what happened, before I was upset).

[Wagnard]

Nope. Not fixed fully



PS. The screenshot state was preceded by multiple launches during the day of application from exclusion list, with long periods of use (several hours in a row).

At the time of the screeshot, no application in the exclusion list was running? You must be 100% certain that there were no process active

No, application didn't start, and it didn't freeze in processes. The purity of the experiment is observed (I myself was surprised by what happened, before I was upset).

I'll investigate more than, maybe there is another bug somewhere.
Just so I can repro appropriately on my end, how many items you have in the exclusion list ?

[vmech]

I'll investigate more than, maybe there is another bug somewhere.
Just so I can repro appropriately on my end, how many items you have in the exclusion list ?

One - vmplayer.exe.
It may be worth noting that between last usage of vmplayer.exe and the discovery of a ISLC dysfunction, the computer was in sleep mode. Normal sleep, not hibernation (hybrid sleep is also disabled).

[Wagnard]

I'll investigate more than, maybe there is another bug somewhere.
Just so I can repro appropriately on my end, how many items you have in the exclusion list ?

One - vmplayer.exe.
It may be worth noting that between last usage of vmplayer.exe and the discovery of a ISLC dysfunction, the computer was in sleep mode. Normal sleep, not hibernation (hybrid sleep is also disabled).

Interesting, this may be a clue.
Thanks

Edit: Do you remember if vmplayer.exe was open when the computer went to sleep ?