#106146: "Game interface locks up after doing any action after sending to server w/ 'waiting for update'"
Hva handler denne rapporten om?
Hva har skjedd, eller hva gjelder det? Vennligst velg
Hva har skjedd, eller hva gjelder det? Vennligst velg
Vennligst sjekk om det allerede er en rapport om samme emne
Hvis ja, vennligst STEM på denne rapporten. Rapporter med flest stemmer er gitt PRIORITET!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detaljert beskrivelse
-
• Vennligst kopier/lim inn feilmeldingen du ser på skjermen, om mulig.
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.
-
• Vennligst forklar hva du ønsket å gjøre, samt hva du faktisk gjorde og hva som skjedde
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 nettleser bruker du?
Google Chrome v119
-
• Vennligst kopier / lim inn teksten som vises på engelsk i stedet for språket ditt. Hvis du har et skjermbilde av denne feilen (alltid lurt) kan du bruke Imgur.com for å laste det opp og kopiere inn lenken til bildet 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 denne teksten tilgjengelig i translation system? Hvis ja, har den blitt oversatt i mer enn 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 nettleser bruker du?
Google Chrome v119
-
• Vennligst forklar ditt forslag nøyaktig og konsistent slik at det er så enkelt som mulig å forstå hva 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 nettleser bruker du?
Google Chrome v119
-
• Hva ble vist på skjermen når du ble blokkert (Tom skjerm? Del av spillgrensesnittet? Feilmelding?)
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 nettleser bruker du?
Google Chrome v119
-
• Hvilken del av reglene ble ikke respektert av 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 regelbruddet tydelig i spilloggen? Hvis ja, Hvilket trekknummer?
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 nettleser bruker du?
Google Chrome v119
-
• Hva var spillhandlingen du ønsket å gjø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.
-
• Hva prøvde du å gjøre for å trigge denne spillhandlingen?
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.
-
• Hva skjer når du prøver å gjøre dette (feilmelding, meldingsstatus for meldingsfelt, ...)?
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 nettleser bruker du?
Google Chrome v119
-
• På hvilket tidspunkt i spillet oppsto problemet (hva var den daværende spillinstruksjonen)?
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.
-
• Hva skjer når du forsøker å gjøre en spillhandling (feilmelding, spillstatusfeltmelding, ...)?
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 nettleser bruker du?
Google Chrome v119
-
• Vennligst beskriv visningsproblemet. Hvis du har et skjermbilde av denne feilen (alltid lurt) kan du bruke Imgur.com for å laste det opp og kopiere inn lenken til bildet 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 nettleser bruker du?
Google Chrome v119
-
• Vennligst kopier / lim inn teksten som vises på engelsk i stedet for språket ditt. Hvis du har et skjermbilde av denne feilen (alltid lurt) kan du bruke Imgur.com for å laste det opp og kopiere inn lenken til bildet 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 denne teksten tilgjengelig i translation system? Hvis ja, har den blitt oversatt i mer enn 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 nettleser bruker du?
Google Chrome v119
-
• Vennligst forklar ditt forslag nøyaktig og konsistent slik at det er så enkelt som mulig å forstå hva 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 nettleser bruker du?
Google Chrome v119
Rapporthistorikk
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.
Legg til noe i denne rapporten
- En annen bord ID / flytt ID
- Løste F5 problemet?
- Oppstod problemet gjentatte ganger? Hver gang? Tilfeldig?
- Hvis du har et skjermbilde av denne feilen (alltid lurt) kan du bruke Imgur.com for å laste det opp og kopiere inn lenken til bildet her.
