DonationCoder.com Software > ProcessTamer

Setting process priority not working with Windows 10?

<< < (6/7) > >>

Erich56:
@Erich56: I'm intrigued by this: Why would the process acemd.exe be changing (lowering) its default priority? This would likely be a deliberate design feature, rather than an error, yet you - the user - clearly don't want it to do that.
I wonder - would it make any difference to the default priority if you set the process to "Run as Administrator"? (Not sure whether that is relevant.)
-IainB (July 14, 2018, 09:52 AM)
--- End quote ---
I don't think that acemd.exe changes it's default priority.  The default priority seems to be "below normal", and what Mouser is suggesting is that once PT changes it to "normal", it's being changed back to "below normal" (after quite variable time spans, which seems strange, anyway).
On all other machines with which I run acemd.exe, there is no problem.  It's just this one PC with an older CPU, where acemd.exe suddenly stopps running. And what I have found out was that this does NOT happen once it's priority is at "normal".
This is the reason behind the whole thing.

mouser:
I think I am suggesting the acemd DOES change it's priority to below normal.  Apps don't start at that priority as far as i know, so it HAS to be that something is setting it low, and I dont think it's PT, so I'm guessing it's the app itself or the process that launched it.

Erich56:
I, too, don't think that PT changes the priority to "below normal" (why should it?).  It must be something else.
Also, on all my other PCs where acemd.exe is running, it's set to "below normal".  However, there it doesn't matter, acemd.exe does not stopp suddenly.
It's only this one machine.  That's why I am so desparately looking for a tool which sets acemd.exe priority to "normal" for the whole time it's running.

IainB:
I don't think that acemd.exe changes it's default priority.  The default priority seems to be "below normal", and what Mouser is suggesting is that once PT changes it to "normal", it's being changed back to "below normal" (after quite variable time spans, which seems strange, anyway).
On all other machines with which I run acemd.exe, there is no problem.  It's just this one PC with an older CPU, where acemd.exe suddenly stopps running. And what I have found out was that this does NOT happen once it's priority is at "normal".
This is the reason behind the whole thing.
-Erich56 (July 14, 2018, 02:48 PM)
--- End quote ---
Ah, that's interesting.

From what you know, does this mean that the default priority of the process/program acemd.exe,  is "below normal" on all computers where it is installed, but that it is just on the single older computer that you suspect that is what causes the program to abend with no(?) error message?

Are all these computers running the same OS and, if not, then what are the differences?
Is there an Event Log for the computer (with the abending process) in question? That might help to identify/indicate a possible root cause of the abend. Similarly, the Event Logs for the other computers might be able to throw some light on the behaviour of the non-abending process' default operation.
At the moment, it seems that you cannot be certain as to what the root cause of the abend actually is. You only know (presumably by trial-and-error) that the abend seems to not occur if the process priority is set to normal. (Is that correct?)

Thus, altering the process priority with PT (Process Tamer) might only be a workaround to an as yet undefined problem, at best.

mouser:
That's why I am so desparately looking for a tool which sets acemd.exe priority to "normal" for the whole time it's running.
--- End quote ---
I will add an option to PT to make it constantly force priority even if the app changes it, just hang in for a couple of days until I post an update :)

Navigation

[0] Message Index

[#] Next page

[*] Previous page