Describe the Bug

On Windows with 1.18, the current zone is constantly rerendered. This is technically fine, but does mean a lot of extra work is being done. There are also a rapid and steep sawtooth pattern of memory usage that seems related, even for a blank campaign that isn't doing anything. This also is not technically a problem as the memory is still reclaimed, but it suggests that something untoward is going on that we don't understand.

To Reproduce

1. Boot up Windows
2. Open up MapTool 1.18.x.
3. Ensure the LibGDX renderer is not in use.
4. Open a blank campaign.
5. Watch the memory usage increase by ~50MiB every second.

Expected Behaviour

When using the Swing renderer, the zone should only render as needed. Memory usage should also be relatively constant when not loading new content or doing other heavy operations.

Screenshots

No response

MapTool Info

1.18.3

Desktop

Linux Mint 22.2

Additional Context

No response