That's pretty drastic! First, please rule out the bug related to '''Accessibility Services'''. That is covered in the reply from philipp in the following thread: [https://support.mozilla.org/questions/1184485 Firefox 57 hangs up]. We have bunch of general support articles with tips that might be useful: * [[Firefox uses too many CPU resources - How to fix]] * [[Firefox hangs or is not responding - How to fix]] * [[Quick fixes if your Firefox slows down]] One point that's interesting is that it sounds like your session after a Refresh is fine, the problem doesn't return until you close Firefox completely and start it up again. Is that what you notice? Firefox has been a multiprocess application since around Firefox 49, and since Firefox 54 it may use four content processes. Firefox uses the first run after installation (or after a Refresh) to assess the system before going into multiprocess mode. So that suggest a test: <p>To help evaluate whether multiprocess is causing problems, or whether the same issue occurs with a single process, you could turn off multiprocess as follows:</p> <p>(1) In a new tab, type or paste <strong>about:config</strong> in the address bar and press Enter/Return. Click the button accepting the risk.</p> <p>(2) In the search box above the list, type or paste <strong>autos</strong> and pause while the list is filtered</p> <p>(3) Double-click the <strong>browser.tabs.remote.autostart.2</strong> preference to switch the value from true to false</p> <p><em>Note: the exact name of the preference may vary, but it will start with browser.tabs.remote.autostart</em></p> <p>At your next Firefox startup, it should run in the traditional way. Any difference?</p>