TIL that using Process Monitor's "Drop Filtered Events" both: - Drops some events that are *not* filtered. - Retains some events that *are* filtered. So yeah, I wouldn't recommend using it if you value your sanity.pic.twitter.com/HQ0c9XK5C5
-
-
I don't have a specific example, but the behavior I see in procmon 3.61 (latest): - Memory usage (and event count) grows for even when events are filtered (not displayed). - Same events that I see happen w/o "Drop Filtered Events" enabled are sometimes not visible when it's on.
-
Does it happen in previous versions too?
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.