But given enough time feeling lost, I will eventually stop and ask for directions. A few weeks ago, that led me to a corner of the browser I’d forgotten about: the plug-ins dialog in Safari’s preferences. As this OS X Daily post reminded me, opening Safari’s prefs, then clicking the Security tab and then its “Plug-in Settings…” button will reveal which random bits of code are active in the browser.

I had forgotten about that because I haven’t intentionally installed a plug-in in years and, long after banishing Oracle’s Java and Adobe’s Flash from this browser, thought I had a clean configuration. Nope! On my iMac, it revealed a Cisco plug-in that I could only blame on a long-ago WebEx session, a SharePoint plug-in or two that my wife might have used for work, a couple of Google Talk plug-ins that I remembered from the occasional “do you want to trust” dialogs, and maybe one for Apple’s QuickTime software.

The results so far have exceeded the placebo effect I expected from changing a setting in an app. The browser is much less likely to jam up my Mac and leave the Activity Monitor app filled with “Safari Web Content” processes lit in red to indicate their unfriendly unresponsiveness.

I’m not done wishing that macOS Sierra would exercise some competent memory management, though. The occasional miscreant page can still zoom to the top of Activity Monitor’s memory-usage graph, while Twitter’s site continues to slowly eat RAM and forces me into a browser restart after maybe two or three days.