#106146: "Game interface locks up after doing any action after sending to server w/ 'waiting for update'"
Hvad handler denne rapport om?
Hvad skete der? Vær venlig og vælg nedenunder
Hvad skete der? Vær venlig og vælg nedenunder
Vær sød at undersøge, om der allerede er sendt en besked om emnet
Hvis ja, venligst STEM for denne rapport. Rapporter med flest stemmer er dem der får PRIORITET!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detaljeret beskrivelse
-
• Venligst kopier/indsæt fejlmeddelelsen du ser på din skærm, hvis der er en.
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.
-
• Venligst forklar hvad du ønsker at gøre, hvad du gjorde og hvad der skete
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.
• Hvilken browser bruger du?
Google Chrome v119
-
• Venligst kopier/indsæt tekst vist på engelsk i stedet for dit sprog. Hvis du har et skærmbillede af denne fejl (god øvelse), kan du bruge Imgur.com til at uploade den og kopiere/indsætte linket her.
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.
-
• er der adgang til denne tekst i oversættelsessystem? Hvis ja, er det blevet oversat inden for 24 timer?
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.
• Hvilken browser bruger du?
Google Chrome v119
-
• Forklar venligst dit forslag præcist og sammenfattende, så det er så let som muligt at forstå, hvad du mener.
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.
• Hvilken browser bruger du?
Google Chrome v119
-
• Hvad blev der vist på skærmen, da du blev blokeret (Blank skærm? Noget af spilbrugerfladen? Fejlmeddelelse?)
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.
• Hvilken browser bruger du?
Google Chrome v119
-
• Hvilken del af reglerne blev ikke respekteret ved BGA-tilpasningen
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.
-
• Er regel-brudddet synligt i e
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.
• Hvilken browser bruger du?
Google Chrome v119
-
• Hvad var den spilhandling du ønskede at udføre?
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.
-
• Hvad forsøgte du at gøre for at udløse denne spilhandling?
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.
-
• Hvad skete der, da du forsøgre at gøre dette (fejlmeddelelse, meddelelsesstatusbjælke, ...)?
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.
• Hvilken browser bruger du?
Google Chrome v119
-
• I hvilket stadie af spillet opstod problemet (hvad var den daværende spilinstruktion)?
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.
-
• Hvad skete der, da du forsøgte at udføre denne spilhandling (fejlmeddelelse, meddelelsesstatusbjælke, ...)?
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.
• Hvilken browser bruger du?
Google Chrome v119
-
• Venligst beskriv display problemet. Hvis du har et skærmbillede af denne fejl (god øvelse), kan du bruge Imgur.com til at uploade den og kopiere/indsætte linket her.
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.
• Hvilken browser bruger du?
Google Chrome v119
-
• Venligst kopier/indsæt tekst vist på engelsk i stedet for dit sprog. Hvis du har et skærmbillede af denne fejl (god øvelse), kan du bruge Imgur.com til at uploade den og kopiere/indsætte linket her.
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.
-
• er der adgang til denne tekst i oversættelsessystem? Hvis ja, er det blevet oversat inden for 24 timer?
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.
• Hvilken browser bruger du?
Google Chrome v119
-
• Forklar venligst dit forslag præcist og sammenfattende, så det er så let som muligt at forstå, hvad du mener.
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.
• Hvilken browser bruger du?
Google Chrome v119
Rapporthistorik
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.
Tilføj noget til denne rapport
- Et andet bord-ID / træk ID
- Løste F5 problemet?
- Skete problemet flere gange? Hver gang? Tilfældigt?
- Hvis du har et skærmbillede af denne fejl (god øvelse), kan du bruge Imgur.com til at uploade den og kopiere/indsætte linket her.
