Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix 68f2213: Don't use GetPoolSize() for end of pool iterator #9461

Merged
merged 1 commit into from Aug 10, 2021

Conversation

glx22
Copy link
Contributor

@glx22 glx22 commented Aug 3, 2021

Motivation / Problem

GetPoolSize() returned value can change during the pool iteration, so using it for end() was not a good idea.

Description

Use a constant (max size of the pool) for end(), and set index to this value whenever it reaches GetPoolSize().

Limitations

Checklist for review

Some things are not automated, and forgotten often. This list is a reminder for the reviewers.

  • The bug fix is important enough to be backported? (label: 'backport requested')
  • This PR affects the save game format? (label 'savegame upgrade')
  • This PR affects the GS/AI API? (label 'needs review: Script API')
    • ai_changelog.hpp, gs_changelog.hpp need updating.
    • The compatibility wrappers (compat_*.nut) need updating.
  • This PR affects the NewGRF API? (label 'needs review: NewGRF')

Copy link
Contributor

@rubidium42 rubidium42 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might solve #9458, but definitely solves a desync via the Vehicle tick counter creating effect vehicles that might not get iterated over.
This as the range based for loop gets end, i.e the original pool size (or actually the highest ID ever assigned), and iterates up to there. If the game already ran a while that highest ID might be significantly higher than the current highest ID, so a joining client would have a lower highest ID, and thus a lower pool size and thus a lower 'value' for end(). This means that in the existing clients the effect vehicle created in the vehicle tick gets iterated over, whereas it does not in the newly joined client causing a divergence in state and eventual desync. Especially as the effect vehicle will be removed earlier, and all assigned vehicle IDs may be off after that event.

@rubidium42 rubidium42 added the backport requested This PR should be backport to current release (RC / stable) label Aug 10, 2021
@glx22 glx22 merged commit 8a083cd into OpenTTD:master Aug 10, 2021
@glx22 glx22 deleted the pool_iterator branch August 10, 2021 17:03
@TrueBrain TrueBrain removed the backport requested This PR should be backport to current release (RC / stable) label Oct 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants