User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0 Build ID: 20160823121617 Steps to reproduce: - I opened the LinkedIn messaging page on their website. - I started a new message. - After typing a few characters, nothing was displayed on the screen anymore. Actual results: The LinkedIn messaging application seems to freeze when the typing is too fast. As a result, nothing gets printed on the screen for a while. Then suddenly everything gets printed at once... Very inconvenient! Expected results: A messaging app (as on Facebook) should work without any time lag... Is the problem on LinkedIn side or on Firefox side?
OS: Unspecified → Windows 7
Hardware: Unspecified → x86_64
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 I have tested this issue on Windows 7 x64 and Windows 10 x64 with the latest Firefox release (48.0.2) and the latest Nightly (51.0a1-20160904030201) and could not reproduce it. After logging in to Linkedin and starting a new message, when typing all the characters are displayed as fast as they are typed. Is this still reproducible on your end? If yes, can you please retest this using the latest Firefox release and the latest Nightly build (https://nightly.mozilla.org/) and report back the results? When doing this, please use a new clean Firefox profile, maybe even safe mode, to eliminate custom settings as a possible cause (https://goo.gl/PNe90E).
Dear Emil, thanks a lot for your feedback. My guess: this is really not caused by the OS but by hardware limitations... My machine is more than 5-year old (Windows performance score: 5.9): how old were yours? After restarting Firefox latest without any activated module or personal preferences (aka "safe mode"), I noticed indeed a slight increase in performance (let say it went from a 3-second lag to a 2-second lag, which is better, but still not satisfactory). I do not think this has to do with a recent bug: I have been experiencing problem with LinkedIn messenger from the day they released it. All other messengers (Facebook, plenty of online chat applications such as Talk.io) are working perfectly fine. But the LinkedIn one seems pretty inefficient. What do you think? Thanks in advance!
I can recreate it with Linux (SUSE LEAP 42.1) using a 4 Core 3.? GHz 8GB RAM system. Further, I am looking for others having problems with FF (I'm currently at 48.0.1). I have problems with Linkedin and trying to read mail. Only the Linkedin header area displays, the text never does. I can pull in the source and I can't seem to find out why I get a gray or white page. I get this with certain other web sites (can't think of one right now besides Linkedin). My point it, I can recreate the OP's complaint on other than a Windows OS system.
Thanks a lot Steve for the feedback! I feel better, I am not the only one... :-) I have experimented with LinkedIn lately, and if I write first my message in MS Windows Notepad, then copy-paste it all at once in the LinkedIn message box, I get nearly a better result (lag-wise). This would imply that it is not the quantity of data entered (the same lag for a short string and a very long string, let say) but rather at the I/O level (something to do with the keyboard events that are saturating an event queue somewhere)... Maybe a test with the brand new FF multi-threaded architecture could be interesting?
I've also noticed this problem on Firefox for Android 48.0 in desktop mode running on Marshmallow on a Rex5260 dev board (~5 second lag between typing and text appearing on-screen). Same sort of lag on Firefox for Android 48.0 and 49.0beta on a Samsung Galaxy Tab 10.1 2014 Edition. Similar problem running Firefox 49.0 on Windows 10 Pro 64-bit (Intel Core i7-6700K @ 4.00 GHz (8 CPUs), 16 GB RAM) with slightly less latency (~2 seconds). For reference, Chrome on Android (Samsung Galaxy Tab 10.1 2014 Edition) had no problem using LinkedIn in desktop mode i.e. no lag. Similarly, Chrome on the same Windows machine had no problem with LinkedIn.
Status: UNCONFIRMED → NEW
Component: Untriaged → General
Ever confirmed: true
OS: Windows 7 → All
Hi, I am setting the Component as General since I find it most appropriate.
platform-rel: --- → ?
You need to log in before you can comment on or make changes to this bug.