1349666 - linux-only deadlock beam.pro - Javascript Timeout

Status: RESOLVED INCOMPLETE

(Core :: JavaScript Engine, defect, P3)

Description

[Feuerstern99]

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" :)

Comment 1

[Feuerstern99]

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.

Comment 2

[YF (Yang)]

https://developer.mozilla.org/en-US/docs/How_to_Report_a_Hung_Firefox

Comment 3

[Feuerstern99]

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...

Comment 4

[Feuerstern99]

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...