- Welcome to Bitsum Community Forum.
Development (period)
News:
NOTICE: Registration may require manual admin activation. After registering visit https://bitsum.com/contact/ to request account activation.
Recent posts
#1
Process Lasso / Re: Question - Define An All P...
Last post by nah1982 - March 22, 2023, 09:27:21 PMQuote from: Jeremy Collake on March 18, 2023, 10:16:06 AMYou can do it using advanced process match Regular Expressions.
You'd create a set of *ordered* rules in the CPU Affinity rules dialog, menu location 'Options / CPU / CPU Affinities...'.
Conceptual example on a CPU with 16 logical cores (threads):
Affinity A = 0-15
Affinity B = 2-15
Pattern Affinity Description /^([^,]*,){3}.*\\windows.*/ Affinity A Processes running from Windows basedir /^([^,]*,)(system),/ Affinity A System user processes /^([^,]*,){2}(chrome\.exe)|(firefox\.exe).*,/ Affinity A An exclusion list, in this case chrome.exe or firefox.exe * Affinity B Match everything else
For some system and protected processes, you may see logged errors where permissions are insufficient to set the affinity. You can ignore those errors, or add those processes to your exclusion list.
If you try it, let me know how it goes!
I will definitely give it a shot this week and let you know how it goes.
Thanks!
#2
Process Lasso / Re: Question - Define An All P...
Last post by Jeremy Collake - March 18, 2023, 10:16:06 AMYou can do it using advanced process match Regular Expressions.
You'd create a set of *ordered* rules in the CPU Affinity rules dialog, menu location 'Options / CPU / CPU Affinities...'.
Conceptual example on a CPU with 16 logical cores (threads):
Affinity A = 0-15
Affinity B = 2-15
For some system and protected processes, you may see logged errors where permissions are insufficient to set the affinity. You can ignore those errors, or add those processes to your exclusion list.
If you try it, let me know how it goes!
You'd create a set of *ordered* rules in the CPU Affinity rules dialog, menu location 'Options / CPU / CPU Affinities...'.
Conceptual example on a CPU with 16 logical cores (threads):
Affinity A = 0-15
Affinity B = 2-15
| Pattern | Affinity | Description |
| /^([^,]*,){3}.*\\windows.*/ | Affinity A | Processes running from Windows basedir |
| /^([^,]*,)(system),/ | Affinity A | System user processes |
| /^([^,]*,){2}(chrome\.exe)|(firefox\.exe).*,/ | Affinity A | An exclusion list, in this case chrome.exe or firefox.exe |
| * | Affinity B | Match everything else |
For some system and protected processes, you may see logged errors where permissions are insufficient to set the affinity. You can ignore those errors, or add those processes to your exclusion list.
If you try it, let me know how it goes!
#3
Process Lasso / Question - Define An All Proce...
Last post by nah1982 - March 16, 2023, 09:07:01 PMI basically want to define a policy that if something isn't a "Microsoft" service/application, or on an exclude list, all processes are pushed to a set of cores.
Can that be done?
It's a pain to manage new / rebuilt installs and new applications / services I wanted restricted to a specific section.
This is for 2x reasons:
1. I prefer to keep everything I can off cores 0&1 to allow Windows room to work; it does wonders for hanging.
2. With CPUs like Ryzen 7950X3D, I'm using ParkControl as I want everything active, but I want to auto force certain things to the non-cache cores unless otherwise directed.
Any feedback or thoughts on how to achieve are appreciated.
Sincerely,
Nathaniel
Can that be done?
It's a pain to manage new / rebuilt installs and new applications / services I wanted restricted to a specific section.
This is for 2x reasons:
1. I prefer to keep everything I can off cores 0&1 to allow Windows room to work; it does wonders for hanging.
2. With CPUs like Ryzen 7950X3D, I'm using ParkControl as I want everything active, but I want to auto force certain things to the non-cache cores unless otherwise directed.
Any feedback or thoughts on how to achieve are appreciated.
Sincerely,
Nathaniel
#4
Process Lasso / Re: Process Lasso crashing whe...
Last post by Aaron44126 - February 23, 2023, 02:21:35 PMUpdated to 12.0.4. Can no longer reproduce this crash. Thanks.
#5
Process Lasso / Re: Process Lasso crashing whe...
Last post by Aaron44126 - February 20, 2023, 08:48:21 AMThanks, and I appreciate the detailed explanation of the issue (as a fellow software engineer). I will check this out soon.
#6
Process Lasso / Re: Process Lasso crashing whe...
Last post by Jeremy Collake - February 19, 2023, 01:54:53 PMProcess Lasso v12.0.4.1 BETA has a fix. The aforementioned mitigation would have also worked.
The issue was in the call to shell32.ExtractAssociatedIcon. One of its parameters, pszIconPath, is a pointer to a non-const buffer holding the pathname to retrieve the icon for. We (I) never paid much attention to it being non-const, and neither have most programmers, as virtually every example of this API, and its sibling ExtractAssociatedIconEx, on the internet is wrong in the same way.
Turns out, it's non-const for a reason: ExtractAssociatedIcon can choose an icon held in a different module than pszIconPath specifies, and in that case, it will will fill the buffer pointed to by pszIconPath with the pathname of the module it actually extracted the icon from.
For files on mapped network drives, an icon is selected from shell32.dll instead of the target executable, so the buffer is filled with shell32's pathname. If that pathname exceeded the original string length, a buffer overflow occurred.
Ultimately, it's poor API design by Microsoft, even at the time it was introduced in XP. The parameter use would have been clarified and buffer overflow prevented if the API accepted a now standard buffer size parameter. Instead, the minimum required size is presumably MAX_PATH, though the documentation doesn't specify such.
The issue was in the call to shell32.ExtractAssociatedIcon. One of its parameters, pszIconPath, is a pointer to a non-const buffer holding the pathname to retrieve the icon for. We (I) never paid much attention to it being non-const, and neither have most programmers, as virtually every example of this API, and its sibling ExtractAssociatedIconEx, on the internet is wrong in the same way.
Turns out, it's non-const for a reason: ExtractAssociatedIcon can choose an icon held in a different module than pszIconPath specifies, and in that case, it will will fill the buffer pointed to by pszIconPath with the pathname of the module it actually extracted the icon from.
For files on mapped network drives, an icon is selected from shell32.dll instead of the target executable, so the buffer is filled with shell32's pathname. If that pathname exceeded the original string length, a buffer overflow occurred.
Ultimately, it's poor API design by Microsoft, even at the time it was introduced in XP. The parameter use would have been clarified and buffer overflow prevented if the API accepted a now standard buffer size parameter. Instead, the minimum required size is presumably MAX_PATH, though the documentation doesn't specify such.
#7
Process Lasso / Re: Process Lasso crashing whe...
Last post by Jeremy Collake - February 19, 2023, 07:44:00 AMI can confirm there is some issue with the GUI in this circumstance. We're still studying it.
It is possible that disabling process icons will work as a temporary mitigation. You can do that by unchecking 'View / Show Process Icons'.
I'll report back when we know more and have a fix.
Thank you!
It is possible that disabling process icons will work as a temporary mitigation. You can do that by unchecking 'View / Show Process Icons'.
I'll report back when we know more and have a fix.
Thank you!
#8
Process Lasso / Process Lasso crashing when a ...
Last post by Aaron44126 - February 15, 2023, 03:56:11 PMI have been able to consistently cause Process Lasso to crash by:
Doesn't matter what program. It crashes every time. It points me to a crash dump location. (146 MB dump, a little big to upload here.)
Things that do not cause it to crash:
I'd speculate that Process Lasso is running something either elevated or as the SYSTEM account, which would not be able to "see" the mapped network drive (mapped drives are user-specific) and it is failing to get some information about the running process because of that.
- Having the Process Lasso window open (list of processes displayed).
- Running a program from a mapped network drive (drive letter pointed to a network share).
Doesn't matter what program. It crashes every time. It points me to a crash dump location. (146 MB dump, a little big to upload here.)
Things that do not cause it to crash:
- Running a program from a mapped network drive while Process Lasso is closed (running in system tray, no window open).
- Running a program from a network share that is NOT mapped to a drive (\\SERVERNAME\SHARENAME\file.exe) while Process Lasso is open.
I'd speculate that Process Lasso is running something either elevated or as the SYSTEM account, which would not be able to "see" the mapped network drive (mapped drives are user-specific) and it is failing to get some information about the running process because of that.
#9
Process Lasso / Re: [Modification] Sorting abi...
Last post by Jeremy Collake - December 21, 2022, 03:07:38 PMSure! Ticket created. We'll try to get to it soon!
#10
Process Lasso / [Modification] Sorting ability...
Last post by Coldblackice - December 20, 2022, 10:00:03 AMWhen using the quick-filter, if a filter is applied, the ability to sort is lost; nothing happens.
Would it be possible to enable the ability to sort filtered results? This would be most useful when filtering for a particular process with multiple instances (or derivative namings) and wanting to sort-compare them with each other via sub-sort the filtered results.
And if/when the filter box is cleared, the prior/default ordering could be restored to the panel.
Would it be possible to enable the ability to sort filtered results? This would be most useful when filtering for a particular process with multiple instances (or derivative namings) and wanting to sort-compare them with each other via sub-sort the filtered results.
And if/when the filter box is cleared, the prior/default ordering could be restored to the panel.