Started by iisaiiah, May 23, 2023, 08:58:47 AM
Quote from: Galandil on July 28, 2023, 09:21:19 PMI'd like to know if using a CPU Set of *,16-31 (or whatever threads ID I choose) leads inexorably to this problem, and the only solution would be to assign manually Sets for each and every process (which, tbh, comes as counterintuitive to me, due to how Sets are supposed to work as explained in the documentation).
Quote from: Jeremy Collake on July 30, 2023, 06:58:40 AMYour broad CPU Sets rule is apparently negatively interacting with a device driver on your system, hence the BSODs. I agree that it doesn't seem like it should, but the enforcement of CPU Sets is done by the OS, and we have no visibility into what is happening. Generally, we don't recommend such broad rules for this very reason.Therefore, your conclusion is correct: You need more targeted rules.
Quote from: Galandil on August 05, 2023, 01:22:26 PMWell, I was mistaken: the system *wasn't* stable, and it wasn't at all PL fault... Apparently, due to my settings in PBO...
QuoteAs a side note: at first PL wouldn't show up, after a boot/reboot, in the system tray, and I had to force a 5 seconds delay in the Task Schedule for both the GUI and the Session Agent. ... Is this a known "semi" issue (not really an issue since it can be easily solved by delaying the start of those processes)?
Quote from: Jeremy Collake on August 07, 2023, 08:06:31 AMThat's unsettling to hear. It is not a known issue. If you get a chance, and haven't already, try removing the delay and just confirm the tray icon loss is consistent, and of course don't forget to check the overflow area, which could be impacted by load order. I mention that only to be thorough.The Governor service (ProcessGovernor.exe) enforces rules, so I have no explanation as to how any GUI startup issue would impact it.Do you have multiple users on the PC? Is your primary user Limited or Admin?In any event, we'll certainly keep an eye out for that!
Quote from: Jeremy Collake on August 08, 2023, 07:45:26 AMlol, well I'm glad it's working alright now! We'll keep chewing it, since an app startup failure like that would be a pretty big deal, even if rare.If you see it happen again, or get any further clues, please do let us know.Never feel bad about reporting issues, regardless of the outcome.
Quote from: Galandil on September 02, 2023, 05:51:05 PMAny idea of what could be that's causing this issue?
QuoteP.S.: I have bought PL, so not using the app in trial anymore.
Quote from: Jeremy Collake on September 04, 2023, 07:33:24 AMIt's hard to say. My first guess has to be that tray overflow area, just because it's the most obvious. Check it carefully if you didn't. The load order with other tray apps might change if it is sent to the overflow area or not. You can drag it down to the usual main area to keep it visible on every run.Assuming it isn't hiding there, *maybe* explorer is crashing and restarting in an inopportune time, causing the loss of the tray icon. Normally Process Lasso can recover from explorer crashes, so the timing would be a big factor if that is the case. To date, we have no other reports, but we are now tracking the issue and will brainstorm on it.Thank you
QuoteIf you need any help regarding this issue, and need me to test stuff, just drop me a PM here.
QuoteIf explorer is crashing, I'd have an Error entry in the Administrative Events of the Event Viewer, right?