Bug in 5.0.0.41: Actions log problem.

[Miroku4444]

I noticed a bug in the actions log table. When i make a setting change(like when you configure probalance behavior parameters), the names(time, process name, PID, action, more info, etc..) in the actions log table disappear. I can get them back by hovering the pointer over them, but why should i have too?

Anybody else experiencing this?

[Jeremy Collake]

Sounds like a window painting/refreshing issue. I've not seen it myself, but I definitely believe you. If anyone else is seeing it, please do post. If you have any software installed that modifies how Windows are painted (e.g. WindowBlinds), that could have an impact - as could your particular video drivers, especially in Vista+ with hardware acceleration enabled.

[Miroku4444]

I have Windows XPSP3, so it could be just an XP issue? My graphics card is a Nvidia GeForce 8300GS.

[hanemach_gt]

It may be XP issue as I reported few months ago that PL didn't show process list, what seemed to be one-shot problem because I can't reproduce that to this day.

[Jeremy Collake]

Strange... Have you seen any other program do this? Since I coded all the window painting 'by hand' instead of using pre-written libraries and such, it is possible something about the way I do it causes this occasional hiccup on some systems. It is going to be very difficult to fix without reproducing though. I will do some research and see what I find.

[Miroku4444]

Strange... Have you seen any other program do this? Since I coded all the window painting 'by hand' instead of using pre-written libraries and such, it is possible something about the way I do it causes this occasional hiccup on some systems. It is going to be very difficult to fix without reproducing though. I will do some research and see what I find.

Do you have a XP system, cause i get the issue everytime i configure the pro-balance behavior parameters or re-start process lasso.

[Jeremy Collake]

I have multiple XP test beds, but they are virtual machines, which means they may differ a bit from a real physical machine. Can you take a screenshot by chance, so I can be certain of what we're speaking of? Screenshot Captor is good, free screenshot software if you don't already have one. Or just hit PrtScr (whole screen) or Alt-PrtScr (current window), then open Paint, and hit CTRL+V. (post edited per michal's note below)

[Miroku4444]

Here's What's Missing:




Should Look Like:

[Jeremy Collake]

That's actually different than I thought, glad I asked for a screenshot. How in the world that could happen ... I don't know.... Very strange. I will look into it, see if I can find any similar things going on with other software, and identify any possible causes. I suspect it isn't isolated to Process Lasso because of all the things I do manually, painting the listview columns is something NOT done manually.

[Miroku4444]

That's actually different than I thought, glad I asked for a screenshot. How in the world that could happen ... I don't know.... Very strange. I will look into it, see if I can find any similar things going on with other software, and identify any possible causes. I suspect it isn't isolated to Process Lasso because of all the things I do manually, painting the listview columns is something NOT done manually.

Could it be a graphic card issue?

[TfH]

Could it be a graphic card issue?

It might be. I dont remember what Catalyst version i used to update to latest. I was too lazy and not completely (yes, stupid me..) uninstalled previous version. I then did that and re-installed latest version. Not seen that problem for very long time. On my rig, when GPU is over 97% utilized, then i see that, but minimize and back to maximized solves it.

So in short, i could say that but not 100% sure it is related to Catalyst. My seconadary machine is having same "issue" when GPU usage is over 97% on latest Catalyst.

EDIT: on older Catalyst there was no that prob. But in older Catalyst was complete freeze and hard reset if GPU usage was +~60% before video started. If GPU usage was lower, no freezing prob.

[Jeremy Collake]

It could be ... BUT, it is all speculation for now. For my part, the only programmatic error I could think of is a child window is overlapping the header of the listview. Such as case could cause variance in behavior between systems. However, that shouldn't be occurring. We'll see, and hopefully find the cause.

[hanemach_gt]

I even have screen refresh stalls from time to time, no matter whether on XP or 7. And just a small tip - to create PrintScreen of current window you just need to press Alt+PrtScn.

[Jeremy Collake]

I even have screen refresh stalls from time to time, no matter whether on XP or 7. And just a small tip - to create PrintScreen of current window you just need to press Alt+PrtScn.

The stalls of the Process Lasso window are a different issue. They occur during high CPU loads and are the same issue that ProBalance addresses. You see the same thing happen to the shell (explorer.exe) when you hit the Windows key during high loads and it takes several seconds for the start menu to appear. While I was writing this reply, noticing the Task Manager was able to keep its graph painting smooth during high loads, it occurred to me what the cause is. It is a design difference, and one that I can resolve -- but it will take a fairly large overhaul. Basically, the graph is too inter-dependent on the process re-enumeration. For each interval, it has to wait for the process list to get updated, and if that takes extra time due to a high CPU load, then the graph appears jerky. In contrast, the Task Manager's graph is isolated from the process enumeration code, causing it to paint smoothly (because it doesn't have to wait). Delays in updating the process list aren't as perceptible.

Since the cause is that inter-dependence, it is also possible that 'jerkiness' in the graph could be caused in other situations, such as the window opening while there is high disk I/O and a high memory load. Again, cosmetic, but important to fix...

I've put this pretty high on the TODO list of the next beta series. It isn't something I can change quickly, as I'll have to regression test everything, but it is something I definitely CAN fix.

As for Alt+Prtscr for current window only.. thanks for reminding me/us .

[Miroku4444]

I don't know if this helps, but hitting the hide graph button also causes this issue.

[Jeremy Collake]

Thanks. I believe I am onto a clue on this, but will report more when I know more for sure.