#3734 "Groupy" software causes trace file being spammed by IsExcluded
-
Accepted
Reproduction steps: Hit F5 (reload) on the Windows desktop while Groupy software is active, this is one way. Since the trace file keeps showing these entries I assume there are many other causes, too.
https://www.stardock.com/products/groupy/
Actual result: KES trace files are spammed with thousands of lines saying:
11:16:08.972 0x1a74 INF ushata ushata IsExcluded checking start
11:16:08.972 0x1a74 INF ushata ushata IsExcluded verdict: false, module = C:\Program Files (x86)\Stardock\Groupy\groupy_32.dll
Expected Result: I assume that the same group_32.dll file should not be checked for exclusion over and over again?
PS: When I share my trace-file here, can every user see the link and thus access it unless I make the report "private"?
System Settings
Operating system: Win 10, x64
System: 5900X, MSI X570, 16 gb, M.2 SSD
Product: KES
Product Version: 11.7.0.609
Language: en-US
Product Logs: https://1drv.ms/u/s!AsEwNk439-yxh5kMhIuycTVrJTBYcQ?e=9WLKza
-
@timur-born said in "Groupy" software causes trace file being spammed by IsExcluded:
PS: When I share my trace-file here, can every user see the link and thus access it unless I make the report "private"?
yes. it's shown for every one.
You can zip your traces and protect it wit password (which can be sent to me in private messages)
or use likns with password protection. (https://cloud.qainfo.ru/ - is our cloud, you can ask for login @ILYA.ZADONSKY in private messages
-
I am sorry, but I clicked on the wrong trace file. The Groupy spam is still present, but it is not in the (up to 5 gb large) SVR trace, but the much smaller GUI trace. The linked trace file is the correct one, but obviously the spam is not half as bad as I thought it would be.
What confused me that the SRV log grows every time I hit F5 on the desktop, so I connected it to Groupy. Just in case I also append the SVR log here (about 30 mb zip file).
https://1drv.ms/u/s!AsEwNk439-yxh5kNXDr2AIh6UzyEdQ?e=0MD3Va