Bug 357997 - sometimes incorrectly reports 0 moves and ends
Summary: sometimes incorrectly reports 0 moves and ends
Status: REPORTED
Alias: None
Product: kdiamond
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Stefan Majewsky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-14 19:30 UTC by Jan Hudec
Modified: 2021-03-09 23:43 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Screenshot of an invalid end (227.73 KB, image/png)
2016-01-14 19:34 UTC, Jan Hudec
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Hudec 2016-01-14 19:30:33 UTC
Sometimes the game counts 0 moves and ends though there are clearly moves left and enough
time left as well. It seems to occur in chain reactions and quite likely in the middle of them as the end game dialog seems to appear before the gems stop moving.

Reproducible: Sometimes

Steps to Reproduce:
1. Play, on very hard, so there are not many options.
2. When the game ends, check whether there are indeed no possible moves.


Actual Results:  
Sometimes, not very often, there clearly are available moves, but the game has ended. It appears as if the game checked for available moves at a moment the gems were not stable yet.

Expected Results:  
The game continues if the stable state reached has valid moves.

See attached screenshot as evidence it happens.
Comment 1 Jan Hudec 2016-01-14 19:34:51 UTC
Created attachment 96643 [details]
Screenshot of an invalid end

The screenshot shows a state where the status bar shows 0 possible moves, clearly not caused by running out of time as there is still 1:42 left, but at least 3 possible moves can be clearly seen: the blue gem in the middle of top row to the left, the same blue gem down and the blue gem near the centre to the right.
Comment 2 Justin Zobel 2021-03-09 23:43:40 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.