Closed
Bug 1344456
Opened 9 years ago
Closed 8 years ago
BEAM.PRO is very resource extensive
Categories
(Core :: DOM: Content Processes, defect)
Tracking
()
People
(Reporter: megarig_2000, Unassigned)
References
()
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0
Build ID: 20170302120751
Steps to reproduce:
Typing on the chat input.
Actual results:
Trying to type on the chat input box is laggy, very uncomfortable.
E10s on and off. Hardware Acceleration on and off.
Expected results:
It should be a smooth experience.
Tested on Maxthon(Webkit engine, not Blink) and SlimJet(Chromium variant) chatting in the field is smooth and responsive.
Note: Weak laptop (A6-6310 SoC, 4GB RAM with 8G ReadyBoost, HDD).
Note 2: Tested on my desktop and its unbearable with e10s disabled, try typing over time and it we have to wait for the letters to finish displaying before continued typing, note that "over time," not when you begin.
Desktop is FX-6300 with 8GB RAM, Samsung 850 EVO SSD.
Both with Windows 10 Home 64-bit. Laptop Firefox 52 BETA RC2 32-bit FX and desktop Firefox 51.0.1 64-bit.
Kudos on Twitch being bearable without e10s on my laptop, seriously a great job. Really smooth with e10s. Testing Palemoon and typing is a bit stuttery at times, so I take it the Twitch portion was fixed on the Firefox's core.
| Reporter | ||
Comment 1•9 years ago
|
||
Don't get me started with e10s disabled on Yahoo! Mail, even my desktop feels that when scrolling through the e-mails but with e10s it is smooth as butter on my laptop and desktop.
| Reporter | ||
Comment 3•9 years ago
|
||
Any streamer page, so just pick one randomly.
But I guess I can use this popular one: https://beam.pro/Monstercat
I also noticed less jank on my desktop. Must be that the developers got working on it, when I reported this 3 weeks ago. Yet, I understand that Maxthon and SlimJet have different engines so it is not an apples-to-apples comparison when indicating "how they perform so well."
I know I might get a reply with "I am not experiencing any problems with the keystrokes," yet the user might be using a more powerful computer, needs to be similar to mine.
For test sake, try to spam your keystrokes and when you have many, press-and-hold the Backspace key, until you clean the input.
I type fast so I catch up to the uncomfortable portion. Happens even when I see the stream player play or not.
| Reporter | ||
Comment 4•9 years ago
|
||
Well, a friend was streaming on HitBox.Tv and all the browsers tanked on my laptop, it's very resource intensive, only gets worse when that site has been this heavy for over a year.
Status: UNCONFIRMED → NEW
Has STR: --- → yes
Ever confirmed: true
Flags: needinfo?(megarig_2000)
Product: Firefox → Core
Comment 5•9 years ago
|
||
Build ID: 20170307030205
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:55.0) Gecko/20100101 Firefox/55.0
Reproducible on Firefox Nightly 55.0a1, 54.0a1, 53.0a1 and 52.0a1 on Windows 10 x 64, Ubuntu 16.04 x64 and on Mac OS X 10.11.
status-firefox52:
--- → affected
status-firefox53:
--- → affected
status-firefox54:
--- → affected
status-firefox55:
--- → affected
Component: Untriaged → DOM: Content Processes
Comment 6•9 years ago
|
||
Too late for firefox 52, mass-wontfix.
| Reporter | ||
Comment 7•9 years ago
|
||
(In reply to Julien Cristau [:jcristau] from comment #6)
> Too late for firefox 52, mass-wontfix.
But is the problem fixed? It still happening to me, while 52.
I think that it is the repainting problem that was happening in YouTube.
Or does anyone know what it is to report it to BEAM?
I have to keep using Chromium or Maxthon because they aren't affected.
| Reporter | ||
Comment 8•9 years ago
|
||
Ah, I see what you did there. I thought since 52 is phased-out, the whole thing is won't fix and ignored.
| Reporter | ||
Comment 9•8 years ago
|
||
This can be closed, they changed their site scripting or something. It's smooth-ish, almost no stops, must be both Mixer's team and Firefox.
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•