#106146: "Game interface locks up after doing any action after sending to server w/ 'waiting for update'"
O czym jest to zgłoszenie?
Co się stało? Wybierz z poniższych opcji
Co się stało? Wybierz z poniższych opcji
Sprawdź, czy istnieje już zgłoszenie na ten sam temat
Jeśli tak, ZAGŁOSUJ na to zgłoszenie. Zgłoszenia z największą liczbą głosów mają najwyższy PRIORYTET!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Szczegółowy opis
-
• Proszę skopiować i wkleić treść błędu wyświetloną na ekranie, o ile jakaś się pojawia.
This happened to both myself and another player on this game, where any action taken would 'send to server', then move to 'waiting for update' and the javascript pinwheel would spin. You could refresh the page and see the action happen, but it would keep doing this. The biggest effect (outside of the annoyance of refreshing everytime you did anything) was that you would not get an option to hide/reveal on explore actions, which is critical i the game.
-
• Proszę opisać co chciałeś zrobić, co zrobiłeś i co się stało
Context: I am a long time software developer and did extensive JS, server to web client work, etc. Contained is some hypothesis which can be completely wrong, but hoping to give enough info to give clues onto where the bug may exist. Happy to answer any/all questions.
Important notes:
When I was in this state, my other game 437998600 was *also* in this state. We created a small test game in addition and it was also in this state after selecting a planet homeworld location.
Things to remediate:
Cleared page cache, used safari instead of chrome, destroyed chrome, updated OS on my macbook.
On both chrome and safari (safari had not been used ever for this site), this state persisted.
For my friend: Clearing page data for boardgamearena fixed the problem for him, for me it did not.
How mine was fixed: This morning, it was working fine. The only action taken was the test game we made was abandoned, I accepted, then when I went to the active table where it was my turn, the problem was gone.
HYPOTHESIS:
For the first time during any game, both my friend and I did a 'scuttle ship' action during the game. After this action the problem emerged. This could be a coincidence. neither of us had encountered this bug before in all our games played.
• Jaką masz przeglądarkę?
Google Chrome v119
-
• Proszę skopiować i wkleić tekst wyświetlany w języku angielskim zamiast w twoim języku. Jeżeli masz zrzut ekranu z tym błędem (dobry zwyczaj) możesz użyć Imgur.com, żeby wrzucić go do Internetu i potem skopiować łącze do niego tutaj.
This happened to both myself and another player on this game, where any action taken would 'send to server', then move to 'waiting for update' and the javascript pinwheel would spin. You could refresh the page and see the action happen, but it would keep doing this. The biggest effect (outside of the annoyance of refreshing everytime you did anything) was that you would not get an option to hide/reveal on explore actions, which is critical i the game.
-
• Czy ten tekst jest dostępny w systemie tłumaczeń? Jeśli tak, to czy został przetłumaczony więcej niż 24 godziny temu?
Context: I am a long time software developer and did extensive JS, server to web client work, etc. Contained is some hypothesis which can be completely wrong, but hoping to give enough info to give clues onto where the bug may exist. Happy to answer any/all questions.
Important notes:
When I was in this state, my other game 437998600 was *also* in this state. We created a small test game in addition and it was also in this state after selecting a planet homeworld location.
Things to remediate:
Cleared page cache, used safari instead of chrome, destroyed chrome, updated OS on my macbook.
On both chrome and safari (safari had not been used ever for this site), this state persisted.
For my friend: Clearing page data for boardgamearena fixed the problem for him, for me it did not.
How mine was fixed: This morning, it was working fine. The only action taken was the test game we made was abandoned, I accepted, then when I went to the active table where it was my turn, the problem was gone.
HYPOTHESIS:
For the first time during any game, both my friend and I did a 'scuttle ship' action during the game. After this action the problem emerged. This could be a coincidence. neither of us had encountered this bug before in all our games played.
• Jaką masz przeglądarkę?
Google Chrome v119
-
• Wyjaśnij swoją propozycję precyzyjnie i zwięźle, tak aby jak najłatwiej zrozumieć, co masz na myśli.
This happened to both myself and another player on this game, where any action taken would 'send to server', then move to 'waiting for update' and the javascript pinwheel would spin. You could refresh the page and see the action happen, but it would keep doing this. The biggest effect (outside of the annoyance of refreshing everytime you did anything) was that you would not get an option to hide/reveal on explore actions, which is critical i the game.
• Jaką masz przeglądarkę?
Google Chrome v119
-
• Co wyświetlało się na ekranie kiedy zostałeś zablokowany (Pusty ekran? Część interfejsu gry? Komunikat o błędzie?)
This happened to both myself and another player on this game, where any action taken would 'send to server', then move to 'waiting for update' and the javascript pinwheel would spin. You could refresh the page and see the action happen, but it would keep doing this. The biggest effect (outside of the annoyance of refreshing everytime you did anything) was that you would not get an option to hide/reveal on explore actions, which is critical i the game.
• Jaką masz przeglądarkę?
Google Chrome v119
-
• Która z zasad gry nie była przestrzegana w adaptacji BGA
This happened to both myself and another player on this game, where any action taken would 'send to server', then move to 'waiting for update' and the javascript pinwheel would spin. You could refresh the page and see the action happen, but it would keep doing this. The biggest effect (outside of the annoyance of refreshing everytime you did anything) was that you would not get an option to hide/reveal on explore actions, which is critical i the game.
-
• Czy naruszenie zasad gry jest widoczne w powtórce rozgrywki? Jeżeli tak, to w ruchu o jakim numerze?
Context: I am a long time software developer and did extensive JS, server to web client work, etc. Contained is some hypothesis which can be completely wrong, but hoping to give enough info to give clues onto where the bug may exist. Happy to answer any/all questions.
Important notes:
When I was in this state, my other game 437998600 was *also* in this state. We created a small test game in addition and it was also in this state after selecting a planet homeworld location.
Things to remediate:
Cleared page cache, used safari instead of chrome, destroyed chrome, updated OS on my macbook.
On both chrome and safari (safari had not been used ever for this site), this state persisted.
For my friend: Clearing page data for boardgamearena fixed the problem for him, for me it did not.
How mine was fixed: This morning, it was working fine. The only action taken was the test game we made was abandoned, I accepted, then when I went to the active table where it was my turn, the problem was gone.
HYPOTHESIS:
For the first time during any game, both my friend and I did a 'scuttle ship' action during the game. After this action the problem emerged. This could be a coincidence. neither of us had encountered this bug before in all our games played.
• Jaką masz przeglądarkę?
Google Chrome v119
-
• Jaką akcję w grze chciałeś wykonać?
This happened to both myself and another player on this game, where any action taken would 'send to server', then move to 'waiting for update' and the javascript pinwheel would spin. You could refresh the page and see the action happen, but it would keep doing this. The biggest effect (outside of the annoyance of refreshing everytime you did anything) was that you would not get an option to hide/reveal on explore actions, which is critical i the game.
-
• Co starasz się zrobić by uruchomić tę akcję w grze?
Context: I am a long time software developer and did extensive JS, server to web client work, etc. Contained is some hypothesis which can be completely wrong, but hoping to give enough info to give clues onto where the bug may exist. Happy to answer any/all questions.
Important notes:
When I was in this state, my other game 437998600 was *also* in this state. We created a small test game in addition and it was also in this state after selecting a planet homeworld location.
Things to remediate:
Cleared page cache, used safari instead of chrome, destroyed chrome, updated OS on my macbook.
On both chrome and safari (safari had not been used ever for this site), this state persisted.
For my friend: Clearing page data for boardgamearena fixed the problem for him, for me it did not.
How mine was fixed: This morning, it was working fine. The only action taken was the test game we made was abandoned, I accepted, then when I went to the active table where it was my turn, the problem was gone.
HYPOTHESIS:
For the first time during any game, both my friend and I did a 'scuttle ship' action during the game. After this action the problem emerged. This could be a coincidence. neither of us had encountered this bug before in all our games played.
-
• Co się stało kiedy próbowałeś to zrobić (komunikat o błędzie, komunikat na pasku stanu gry, ...)?
It won't update the local game state, and instead spins with the pinwheel.
HYPOTHESIS:
Since this seemed to happen cross browser and cross game, it reminded of of times when I infinitely looped in my code and it didn't break out. I'm assuming that some cross game state gets sent down from the server and maybe gets stuck in a loop preventing it from updating. Given it happened in google and safari, it indicates to me the problem may be in how the data being sent down is structured then looped through.
Another guess would be the action of removing a token on this game with 'scuttle ship' might trigger some weird state where it is still referenced, but not having opened up or run the developer debug on this, I'm taking a wild guess.
• Jaką masz przeglądarkę?
Google Chrome v119
-
• W którym momencie gry pojawił się problem (jakie było aktualne polecenie w grze)?
This happened to both myself and another player on this game, where any action taken would 'send to server', then move to 'waiting for update' and the javascript pinwheel would spin. You could refresh the page and see the action happen, but it would keep doing this. The biggest effect (outside of the annoyance of refreshing everytime you did anything) was that you would not get an option to hide/reveal on explore actions, which is critical i the game.
-
• Co się stało kiedy próbowałeś wykonać akcję w grze (komunikat o błędzie, komunikat na pasku stanu gry, ...)?
Context: I am a long time software developer and did extensive JS, server to web client work, etc. Contained is some hypothesis which can be completely wrong, but hoping to give enough info to give clues onto where the bug may exist. Happy to answer any/all questions.
Important notes:
When I was in this state, my other game 437998600 was *also* in this state. We created a small test game in addition and it was also in this state after selecting a planet homeworld location.
Things to remediate:
Cleared page cache, used safari instead of chrome, destroyed chrome, updated OS on my macbook.
On both chrome and safari (safari had not been used ever for this site), this state persisted.
For my friend: Clearing page data for boardgamearena fixed the problem for him, for me it did not.
How mine was fixed: This morning, it was working fine. The only action taken was the test game we made was abandoned, I accepted, then when I went to the active table where it was my turn, the problem was gone.
HYPOTHESIS:
For the first time during any game, both my friend and I did a 'scuttle ship' action during the game. After this action the problem emerged. This could be a coincidence. neither of us had encountered this bug before in all our games played.
• Jaką masz przeglądarkę?
Google Chrome v119
-
• Proszę opisać problem z wyświetlaniem. Jeżeli masz zrzut ekranu z tym błędem (dobry zwyczaj) możesz użyć Imgur.com, żeby wrzucić go do Internetu i potem skopiować łącze do niego tutaj.
This happened to both myself and another player on this game, where any action taken would 'send to server', then move to 'waiting for update' and the javascript pinwheel would spin. You could refresh the page and see the action happen, but it would keep doing this. The biggest effect (outside of the annoyance of refreshing everytime you did anything) was that you would not get an option to hide/reveal on explore actions, which is critical i the game.
• Jaką masz przeglądarkę?
Google Chrome v119
-
• Proszę skopiować i wkleić tekst wyświetlany w języku angielskim zamiast w twoim języku. Jeżeli masz zrzut ekranu z tym błędem (dobry zwyczaj) możesz użyć Imgur.com, żeby wrzucić go do Internetu i potem skopiować łącze do niego tutaj.
This happened to both myself and another player on this game, where any action taken would 'send to server', then move to 'waiting for update' and the javascript pinwheel would spin. You could refresh the page and see the action happen, but it would keep doing this. The biggest effect (outside of the annoyance of refreshing everytime you did anything) was that you would not get an option to hide/reveal on explore actions, which is critical i the game.
-
• Czy ten tekst jest dostępny w systemie tłumaczeń? Jeśli tak, to czy został przetłumaczony więcej niż 24 godziny temu?
Context: I am a long time software developer and did extensive JS, server to web client work, etc. Contained is some hypothesis which can be completely wrong, but hoping to give enough info to give clues onto where the bug may exist. Happy to answer any/all questions.
Important notes:
When I was in this state, my other game 437998600 was *also* in this state. We created a small test game in addition and it was also in this state after selecting a planet homeworld location.
Things to remediate:
Cleared page cache, used safari instead of chrome, destroyed chrome, updated OS on my macbook.
On both chrome and safari (safari had not been used ever for this site), this state persisted.
For my friend: Clearing page data for boardgamearena fixed the problem for him, for me it did not.
How mine was fixed: This morning, it was working fine. The only action taken was the test game we made was abandoned, I accepted, then when I went to the active table where it was my turn, the problem was gone.
HYPOTHESIS:
For the first time during any game, both my friend and I did a 'scuttle ship' action during the game. After this action the problem emerged. This could be a coincidence. neither of us had encountered this bug before in all our games played.
• Jaką masz przeglądarkę?
Google Chrome v119
-
• Wyjaśnij swoją propozycję precyzyjnie i zwięźle, tak aby jak najłatwiej zrozumieć, co masz na myśli.
This happened to both myself and another player on this game, where any action taken would 'send to server', then move to 'waiting for update' and the javascript pinwheel would spin. You could refresh the page and see the action happen, but it would keep doing this. The biggest effect (outside of the annoyance of refreshing everytime you did anything) was that you would not get an option to hide/reveal on explore actions, which is critical i the game.
• Jaką masz przeglądarkę?
Google Chrome v119
Historia zgłoszeń
NOTE: Since I'm not suffering from this bug actively now (who knows how it fixed itself), I'm not scrambling to fix it, but it's pretty gnarly :)
Your bug has probably been fixed already, or was linked to a temporary failure of BGA service.
In any case, when filling a bug report, make sure to have an explicit title linked to the incident (ex: with error message), so other players can recognize it and vote for it.
Dodaj coś do tego zgłoszenia
- Kolejne ID stołu / ID ruchu
- Czy F5 rozwiązało problem?
- Czy problem zdarzył się kilka razy? Za każdym razem? Losowo?
- Jeżeli masz zrzut ekranu z tym błędem (dobry zwyczaj) możesz użyć Imgur.com, żeby wrzucić go do Internetu i potem skopiować łącze do niego tutaj.
