Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

hangs....must bring another window up to recover

  • 2 replies
  • 1 has this problem
  • 5 views
  • Paskiausią atsakymą parašė RicPic

more options

1. Firefox 57-58.01 occasionally hangs on Windows 10 2017 Surface Pro (I5/256gb) 2. As soon as I wake up another window and return to Firefox previous unresponsive clicks were acted upon and Firefox resumes normal operation

This happens routinely. This could very well be a windows touch issue however I am not experiencing this with other apps. My professional experience suggests this is indeed a Firefox issue but then again I could be wrong.

Lastly I have done a multitude of workarounds (e.g. refresh, hardware acceleration and so on) none of which eliminates the issue. I thought I bring this up to see if others have experienced the same issue. Thanks

1. Firefox 57-58.01 occasionally hangs on Windows 10 2017 Surface Pro (I5/256gb) 2. As soon as I wake up another window and return to Firefox previous unresponsive clicks were acted upon and Firefox resumes normal operation This happens routinely. This could very well be a windows touch issue however I am not experiencing this with other apps. My professional experience suggests this is indeed a Firefox issue but then again I could be wrong. Lastly I have done a multitude of workarounds (e.g. refresh, hardware acceleration and so on) none of which eliminates the issue. I thought I bring this up to see if others have experienced the same issue. Thanks

All Replies (2)

more options
more options

Thanks for your prompt reply. I have tried most of these including a Firefox refresh.

Honestly I was just wondering if any other folks have experienced the exact same thing.

The workaround is simple enough (force Firefox to regain focus) but it seems that Firefox has lost focus when it shouldn't. Again this very well could be a Windows 10 issue.

Thanks again.