Fix: Memory leak of airport tile layout in AirportChangeInfo (prop 0A) #8928
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation / Problem
This fixes the long-standing memory leak in AirportChangeInfo (prop 0A) introduced by 917d4cb.
This leak is entirely harmless, so I'd ignored it until now, but having it logged every time is a bit annoying, so it's fixed now.
Use an airport GRF such as OpenGFX+ Airports to reproduce the leak.
Leak details
Description
When replacing AirportSpec::table in AirportChangeInfo (prop 0A), free the old tables instead of leaking them.
Limitations
N/A
Checklist for review
Some things are not automated, and forgotten often. This list is a reminder for the reviewers.