source.setUrl does not abort in-flight raster tile requests (tilejson completed)

[terraputix]

maplibre-gl-js version: 5.18.0

browser: Firefox, Chromium

Summary

Calling source.setUrl(...) on a raster source does not abort in-flight raster tile requests if the tilejson request has already completed. The abort only occurs if setUrl is called before the tilejson response arrives. As a result, the map continues loading tiles from the old URL(s) after setUrl is invoked.

Steps to Trigger Behavior

1. Add a raster source and raster layer.
2. Wait until the tilejson request completes (so tile URLs are known) but before all raster tiles have finished loading.
3. Call source.setUrl(newUrl).
4. Observe that in-flight raster tiles continue to load for the previous URL(s).

Link to Demonstration

Example demonstrating this behavior using a custom protocol: https://gist.github.com/terraputix/cbc40bbf92612e9c13fd795ab1eef247

If the source is removed and re-added the inflight tile-requests are correctly aborted: https://gist.github.com/terraputix/9fa7f1b6168b61ae9187c20d49f98c39. This mitigates my problem, but avoiding visual flickering using this pattern is tedious.

Expected Behavior

Abort inflight tile requests for previous URL when setUrl is called.

Actual Behavior

Inflight requests are only aborted if setUrl is called before the tilejson is returned.

[terraputix]

Just wanted to add here that I also tried the following hacks with limited success:

const tileManager = map.style.tileManagers[tileSource.id];

// seems to abort the tile requests, but will also always unload all currently visible tiles leading to visual flickering
tileManager.clearTiles()

// does not abort requests of pending tiles
tileManager._outOfViewCache.reset() 

// does not abort requests of pending tiles
for (const id of tileManager._inViewTiles.getAllIds()) {
    const tile =
        tileManager._inViewTiles.getTileById(id);
    tileManager._abortTile(id);
}

// does not abort requests of pending tiles
tileManager.reload(true);

If there is something I am obviously doing wrong, I'd be happy to be corrected.

With some pointers where to look, I would also be willing to submit a PR to fix this issue.

[HarelM]

Thanks for taking the time to open this issue.
The logic of loading tiles and aborting them resides in raster_tile_source.ts inside the loadTile method.
This is called from the tileManager according to tiles that are currently in view or moved to be out of view.
Feel free to poke around there and try to fix this issue.
Generally speaking, concurrent code flows are always hardest to fix/debug/get right.

[pcardinal]

Is it what you are looking for ?

Enregistrement.2026-02-28.175723.mp4

[pcardinal]

should I do the PR?

[HarelM]

Feel free to do so. Make sure you add the relevant tests.