linux-only deadlock beam.pro - Javascript Timeout

UNCONFIRMED
Unassigned

Status

()

Core
JavaScript Engine
P3
critical
UNCONFIRMED
8 months ago
2 months ago

People

(Reporter: Feuerstern99, Unassigned)

Tracking

({hang, triage-deferred})

52 Branch
Unspecified
Linux
hang, triage-deferred
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

8 months ago
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0
Build ID: 20170316213829

Steps to reproduce:

I'm using Firefox for Ubuntu - KUbuntu 16.10 - Linux 4.8.0-41 - 64-bit
I have issues with the NVidia-Driver anyway, because I have a non-standart GPU, may have something to do with that. (Video decoding enters infinite loop randomly)

- go to beam.pro
- go on someone to watch it's livestream
- click on a recorded livestream underneath the main livestream to watch that


Actual results:

- display doesn't update (window doesn't react or recieves any events)
- looks like a deadlock
- can still be closed with a TERM-Signal to process


Expected results:

no "deadlock" :)
(Reporter)

Comment 1

8 months ago
After updating firefox (a new update came out) Firefox suddenly showed an "error" message: A Javascript Timeout of script:

chrome://global/content/bindings/browser.xml

The Window reporting it also didn't react anymore...
So it seems like that some internal Firefox script is entering a infinite loop while having a lock. That causes the browser itself to not react anymore. But I noticed that you can interact with Parts of the Website, like pausing the video, but not scrolling or clicking links or other.
(Reporter)

Updated

8 months ago
Summary: linux-only deadlock beam.pro → linux-only deadlock beam.pro - Javascript Timeout

Comment 2

8 months ago
https://developer.mozilla.org/en-US/docs/How_to_Report_a_Hung_Firefox
Severity: normal → critical
Keywords: hang
OS: Unspecified → Linux
(Reporter)

Comment 3

8 months ago
Thanks for replying :)

Got the crash-report here:
https://crash-stats.mozilla.com/report/index/2dd0d729-9fb8-48f0-bedf-55d8f2170325#tab-details

I didn't see that article when I was looking around. 
BTW the "create bug report" links as the last step of each OS are all broken...

Updated

8 months ago
Component: Untriaged → JavaScript Engine
Product: Firefox → Core
(Reporter)

Comment 4

7 months ago
It has been almost a month now and I wanted to ask if there will be anything happening? Especially because one of you set it on critical...
Keywords: triage-deferred
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.