#106146: "Game interface locks up after doing any action after sending to server w/ 'waiting for update'"
Worum geht es bei dieser Meldung?
Was ist passiert? Bitte wähle unten aus
Was ist passiert? Bitte wähle unten aus
Bitte überprüfe, ob bereits eine Meldung zum gleichen Thema existiert
Wenn ja, STIMME bitte für diese Meldung. Meldungen mit mehr Stimmen erhalten höhere PRIORITÄT!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detaillierte Beschreibung
-
• Falls du eine Fehlermeldung auf dem Bildschirm siehst, bitte kopieren und einfügen.
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.
-
• Bitte erkläre, was du machen wolltest, was du dann getan hast und was dann passiert ist
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.
• Welchen Browser benutzt du?
Google Chrome v119
-
• Bitte kopiere den Text, der in Englisch anstatt in deiner Sprache angezeigt wird, und füge ihn hier ein. Falls du einen Screenshot dieses Fehlers hast (optimale Vorgehensweise), kannst du ihn bei Imgur.com hochladen, den Link kopieren und hier einfügen.
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.
-
• Ist dieser Text auf der Übersetzungsseite verfügbar? Wenn ja, wurde dieser vor mehr als 24 Stunden übersetzt?
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.
• Welchen Browser benutzt du?
Google Chrome v119
-
• Bitte erkläre deinen Vorschlag so präzise und genau wie möglich, damit er leicht zu verstehen ist.
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.
• Welchen Browser benutzt du?
Google Chrome v119
-
• Was wurde auf dem Bildschirm angezeigt, als du blockiert wurdest (weißer Bildschirm? Teil der Spieloberfläche? Fehlermeldung?)
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.
• Welchen Browser benutzt du?
Google Chrome v119
-
• Welcher Teil der Spielregel wurde durch die BGA-Adaption nicht beachtet?
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.
-
• Ist der Regelverstoß in der Spielwiederholung zu sehen? Falls ja, bei welcher Zugnummer?
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.
• Welchen Browser benutzt du?
Google Chrome v119
-
• Welche Spielaktion wolltest du durchführen?
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.
-
• Was versuchst du, um diese Spielaktion auszulösen?
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.
-
• Was passiert, wenn du dies versuchst (Fehlermeldung, Statusmeldung des Spiels, ...)?
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.
• Welchen Browser benutzt du?
Google Chrome v119
-
• An welcher Stelle im Spiel ist das Problem aufgetreten? Was war die aktuelle Spielanweisung?
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.
-
• Was passiert, wenn du die Spielaktion ausführen möchtest (Fehlermeldung, Statusmeldung des Spiels, ...)?
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.
• Welchen Browser benutzt du?
Google Chrome v119
-
• Bitte beschreibe die Anzeigeschwierigkeiten. Falls du einen Screenshot dieses Fehlers hast (optimale Vorgehensweise), kannst du ihn bei Imgur.com hochladen, den Link kopieren und hier einfügen.
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.
• Welchen Browser benutzt du?
Google Chrome v119
-
• Bitte kopiere den Text, der in Englisch anstatt in deiner Sprache angezeigt wird, und füge ihn hier ein. Falls du einen Screenshot dieses Fehlers hast (optimale Vorgehensweise), kannst du ihn bei Imgur.com hochladen, den Link kopieren und hier einfügen.
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.
-
• Ist dieser Text auf der Übersetzungsseite verfügbar? Wenn ja, wurde dieser vor mehr als 24 Stunden übersetzt?
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.
• Welchen Browser benutzt du?
Google Chrome v119
-
• Bitte erkläre deinen Vorschlag so präzise und genau wie möglich, damit er leicht zu verstehen ist.
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.
• Welchen Browser benutzt du?
Google Chrome v119
Meldungshistorie
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.
Ergänze diese Meldung
- Eine weitere Tisch-ID/Zug-ID
- Konnte F5 das Problem lösen?
- Trat das Problem öfter auf? Jedes Mal? Zufällig?
- Falls du einen Screenshot dieses Fehlers hast (optimale Vorgehensweise), kannst du ihn bei Imgur.com hochladen, den Link kopieren und hier einfügen.
