#106146: "Game interface locks up after doing any action after sending to server w/ 'waiting for update'"
Despre ce este vorba acest raport?
Ce s-a întâmplat? Te rugăm alege de mai jos
Ce s-a întâmplat? Te rugăm alege de mai jos
Verificați dacă există deja un raport privind același subiect
Dacă da, te rugăm VOTEAZĂ pentru acest raport. Rapoartele cu cele mai multe voturi au PRIORITATE!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Descriere detaliată
-
• Te rugăm copiază/lipeşte mesajul erorii pe care îl vezi pe ecran, dacă apare vreunul.
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.
-
• Explică, te rugăm, ce ai vrut să faci, ce ai făcut, și ce s-a întâmplat
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.
• Care e browserul tău?
Google Chrome v119
-
• Va rugam copiati/lipiti textul afisat in engleza in locul limbii dumneavoastra. Dacă ai o captură de ecran cu acest bug (ceea ce îți sugerăm), poți folosi Imgur.com pentru încărcarea imaginii și pentru a pune link-ul aici.
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.
-
• Este textul acesta disponibil în sistemul de traduceri? Dacă da, a fost tradus mai recent de 24 de ore?
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.
• Care e browserul tău?
Google Chrome v119
-
• Vă rugăm să explicați sugestia exact și concis, astfel încât să fie cât mai ușor de înțeles.
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.
• Care e browserul tău?
Google Chrome v119
-
• Ce a fost afișat pe ecran atunci când ai fost blocat (Ecran gol? O parte din interfața jocului? Mesaj de eroare?)
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.
• Care e browserul tău?
Google Chrome v119
-
• Care parte din reguli nu a fost respectată de adaptarea 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.
-
• Se observă frauda când derulați reluarea? Dacă da, la a câta mutare?
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.
• Care e browserul tău?
Google Chrome v119
-
• Care a fost acțiunea pe care ai vrut să o faci?
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.
-
• Ce ai făcut de ai produs această reacție/eroare?
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.
-
• Ce se întâmplă atunci când vrei să faci asta (apare o eroare, un mesaj din partea jocului in partea de sus a ecranului, ...)?
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.
• Care e browserul tău?
Google Chrome v119
-
• În ce etapă a jocului a apărut eroarea (care era instrucțiunea din acel moment) ?
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.
-
• Ce se întâmplă atunci când vrei să acționezi în joc (apare o eroare, un mesaj din partea jocului in partea de sus a ecranului, ...)?
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.
• Care e browserul tău?
Google Chrome v119
-
• Descrieți, vă rugăm, problema de afișaj. Dacă ai o captură de ecran cu acest bug (ceea ce îți sugerăm), poți folosi Imgur.com pentru încărcarea imaginii și pentru a pune link-ul aici.
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.
• Care e browserul tău?
Google Chrome v119
-
• Va rugam copiati/lipiti textul afisat in engleza in locul limbii dumneavoastra. Dacă ai o captură de ecran cu acest bug (ceea ce îți sugerăm), poți folosi Imgur.com pentru încărcarea imaginii și pentru a pune link-ul aici.
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.
-
• Este textul acesta disponibil în sistemul de traduceri? Dacă da, a fost tradus mai recent de 24 de ore?
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.
• Care e browserul tău?
Google Chrome v119
-
• Vă rugăm să explicați sugestia exact și concis, astfel încât să fie cât mai ușor de înțeles.
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.
• Care e browserul tău?
Google Chrome v119
Raportează istoric
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.
Adaugă ceva la acest raport
- Alt identificator de masă / de mutare
- A rezolvat F5 problema?
- Această problemă a apărut de mai multe ori? De fiecare dată? Ocazional?
- Dacă ai o captură de ecran cu acest bug (ceea ce îți sugerăm), poți folosi Imgur.com pentru încărcarea imaginii și pentru a pune link-ul aici.
