Ajax connection makes page freeze for 2-3 seconds
opened this issue · comments
I'm opening a seperated issue on this because it's more annoying than I first thought. It's really a big problem. JSXC seem to consume more resources now than before. :/
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Can someone confirm that? I have no problems on my Thinkpad Edge 11
I may come from the server though, the JS script freezes until the server answers. As sechat.org is smaller than diaspora-fr.org. So it may answer more quickly.
I've uploaded you a video here so you can see how it's like. On the video, the page freezes for about 3 seconds but it's sometimes 4 or 6.
@zauberstuhl you have an account on d-fr right? You can use this invitation link if you need: https://diaspora-fr.org/i/d24d8737f3a9
Nope I have also no problems with my diaspora-fr account. how many contacts do you have in the chat? If you add all your contacts (1k+) at once I am pretty sure your browser needs some time rendering it (plus the double contact bug).
something like ~200 in my 3 aspects where the chat is activated.
I have ~50 contacts which I don't think this is a big amount. That's why I'm concerned on this. It happens on pretty much each page loading, this is a big ergonomic issue to me.
I just deactivated temporary the chat on d-fr and I confirm that the page is not freezing anymore, even if I still find it pretty slown to load. Damn...
It's only on connection. We have to find a way to lighten the connection function.
@jhass his reference is valid, I had this problem in the past as well. Clearing the pod its cache and your own browser temporary solves it.
@zauberstuhl this issue is true my hardware specs:
- Debian 8 (Jessie/Testing)
- Asus Rampage Extreme IV
- Intel i7 920 @ 4.133 GHz
- 12GB DDR 3 Corsair Vengeance (I believe)
- Saphire R9 280 Dual Vapor X
My issue's:
Whole browser turns slow when it is loaded for longer period of times. It fills my RAM up to 6 to 8 GB of memory and eventually FireFox crashes. Crashes happens when having FireFox loaded for extensive amount of time and mostly in combination of HTML5 Web Players for example at crunchyroll.com