Don’t spam with OutputDebugString
Posted by jpluimers on 2012/09/13
A production version of an app should not spam using OutputDebugString.
Some apps do, for instance very couple of seconds the “TAM E-SSO AccessAgent” DataProvider.exe process spams stuff like this:
[1952] GRP_StubImpl Inside [1952] before deserializing the message [1952] GRP_StubImpl for Policy Id = pid_desktop_inactivity_mins ... [1952] GRP_StubImpl Inside [1952] before deserializing the message [1952] GRP_StubImpl for Policy Id = pid_aa_tray_menu_options_enabled [1952] GRP_StubImpl Inside [1952] before deserializing the message [1952] GRP_StubImpl for Policy Id = pid_automatic_sign_up_enabled [1952] GRP_StubImpl Inside [1952] before deserializing the message [1952] GRP_StubImpl for Policy Id = pid_desktop_inactivity_mins ...
It is in the chain of processes (yes, the tripple backslash is actually there, this is how IBM starts is):
- “C:\Program Files\Encentuate\AATray.exe”
- “C:\Program Files\Encentuate\\\DataProvider.exe”
- “C:\Program Files\Encentuate\Sync.exe”
- “C:\Program Files\Encentuate\\\DataProvider.exe”
All of them have version 8.1.0.130 and timestamp 20-12-2010 14:32.
You’d think that IBM knows how to do this right (:
–jeroen
The Wiert Corner - irregular stream of stuff 
Leave a comment