@Cezary_Wagner
Thank you my friend!
Thank you my friend!
The problem might be hardware related. I find that v2 lags/stutters for me on my little netbook (E200-HA series) whereas it runs ok on my desktop and bigger laptop. It seems that v2 is more resource hungry or something. The low responsiveness means I can just about play 3+2, but it is near impossible to gain time.
I don't think it has any connection in my case. My PC has i7 6700k intel cpu, 16 GB ddr4 3000hz RAM and a geforce 1060 GPU. It should be more than enough for a chess app.
My computer is much stronger than @orior so it is not problem with hardware.
Next game with freezing clock - clock stops.
After browser refresh F5 clock go alive when I have 10s.
How to win blitz. Latency 86ms but clock freeze for 30s! (100x more at least).
After browser refresh F5 clock go alive when I have 10s.
How to win blitz. Latency 86ms but clock freeze for 30s! (100x more at least).
Next game lost - browser shows disconnect in middle game after reconnect I do some moves and I cannot win game since extreme lags at end of game ...
20s takes move which take me 1s.
lichess.org/lag -> 4ms/100ms by why it disconnects ...
Last log from ADSL is now is (23:00):
5/28/2019 14:5:24> netMakeChannDial: err=-3000 rn_p=8048e7d8
When I sending this message I see reconnecting too. I am using FF.
20s takes move which take me 1s.
lichess.org/lag -> 4ms/100ms by why it disconnects ...
Last log from ADSL is now is (23:00):
5/28/2019 14:5:24> netMakeChannDial: err=-3000 rn_p=8048e7d8
When I sending this message I see reconnecting too. I am using FF.
I have yesterday experienced that same problem of Cezary_Wagner with the freezing screen and extreme lag. E.g. this game:
Today, I do not dare to play because of this.
Today, I do not dare to play because of this.
@Cezary_Wagner Contact your ISP.
I am programmer (programming network protocols also) and I think that is not problem of ISP but problem of network protocol used by Lichess.
Why network frame is show on my side as send and my browser not retry connection if move is not done?
Why I have to press F5 when protocol hangs to be sure that move is send or not?
Why clocks stop/freezing running?
It is because current protocol not care if move is send (is not transactional) OR protocol is designed as transactional but there is BUG - hard state to predict. Loss of packet is normal thing in internet.
My ISP Orange will not help since they deliver poor quality in Poland and really not care about it too much.
I will call them 10-20x time to solve one problem. They even drop my service request not only packets :)
Currently It works like that:
1. Move send (packet lost - it waits maybe 20s to retry - pings are perfect connection is not broken).
2. If I hit F5/refresh I have high chance to see that move is lost/drop.
3. I do move again manually (protocol should retry as fast as possible).
2a. Alternatively I wait for resend but it is very slow comparing to F5/refresh is fast (20s).
The problem is that I do not know if hit F5 or wait since clocks show that move is done :)
I see today some box "reconnecting" bottom/left - strange that in one window I see reconnecting not in both with lichess - it looks like disconnection is not synchronuous and depend on each FF window.
Why network frame is show on my side as send and my browser not retry connection if move is not done?
Why I have to press F5 when protocol hangs to be sure that move is send or not?
Why clocks stop/freezing running?
It is because current protocol not care if move is send (is not transactional) OR protocol is designed as transactional but there is BUG - hard state to predict. Loss of packet is normal thing in internet.
My ISP Orange will not help since they deliver poor quality in Poland and really not care about it too much.
I will call them 10-20x time to solve one problem. They even drop my service request not only packets :)
Currently It works like that:
1. Move send (packet lost - it waits maybe 20s to retry - pings are perfect connection is not broken).
2. If I hit F5/refresh I have high chance to see that move is lost/drop.
3. I do move again manually (protocol should retry as fast as possible).
2a. Alternatively I wait for resend but it is very slow comparing to F5/refresh is fast (20s).
The problem is that I do not know if hit F5 or wait since clocks show that move is done :)
I see today some box "reconnecting" bottom/left - strange that in one window I see reconnecting not in both with lichess - it looks like disconnection is not synchronuous and depend on each FF window.
Errors logged in FF console:
Połączenie z wss://socket.lichess.org:9026/n6WN7OsFCxzy/socket/v4?sri=ykd6ivkywj&v=0 zostało przerwane podczas wczytywania strony.
Translation:
Connection to wss://socket.lichess.org:9026/n6WN7OsFCxzy/socket/v4?sri=ykd6ivkywj&v=0 was interrupted while loading the page.
Połączenie z wss://socket.lichess.org:9026/n6WN7OsFCxzy/socket/v4?sri=ykd6ivkywj&v=0 zostało przerwane podczas wczytywania strony.
Translation:
Connection to wss://socket.lichess.org:9026/n6WN7OsFCxzy/socket/v4?sri=ykd6ivkywj&v=0 was interrupted while loading the page.
This topic has been archived and can no longer be replied to.