Closed Bug 1327521 Opened 6 years ago Closed 6 years ago

(e10s-specific) Firefox completely hangs/freezes and takes all opened applications and OS Win7_64 with it

Categories

(Firefox :: Untriaged, defect)

defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: arni2033, Unassigned)

Details

Attachments

(1 file)

>>>   My Info:   Win7_64, Nightly 49, 32bit, ID 20160526082509
STR_1:
1. Open attached "testcase 1"

AR:  Firefox hangs and freezes all opened applications and OS itself
ER:  Firefox shouldn't hang, just like GoogleChrome

Note:
1) This bug was filed for Firefox developers to prevent OS hang, unless they think that it's expected
   from e10s browser. It's not up to me to decide how you want to prevent the hang, but there's at
   least one option: to show "crashed tab" dialog with explanation, just like GoogleChrome does.
2) AR isn't completely accurate. If you spent 5-15 minutes near hang PC, you'll notice that sometimes
   mouse pointer responds to mouse movements, so in 15 minutes you'll manage to kill all Firefox
   related processes and get your PC back. If this is intended workflow, please tell that explicitly.
No longer blocks: 1277113
User Agent 	Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:54.0) Gecko/20100101 Firefox/54.0
Build ID 	20170129110302

I haven't managed to reproduce the issue on the latest Firefox release (51.0.1), the latest Nightly (54.0a1) or Nightly 49.0a1 (20160526082509). When the Script is loaded in a tab the browser starts to hang, but it doesn't affect other programs and applications, I was able to switch to other applications without issue. And after 15-40 seconds, depending on the version I used, the browser becomes fully responsive again.

Since the reporter's account is disabled and I cannot reproduce, I will mark the issue as Resolved-Incomplete. If anyone can still reproduce on the latest Firefox version, please feel free to reopen and provide more information.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.