Bug: DOMException: signal is aborted without reason about 3dtilesrendererjs HOT 2 CLOSED

Aborting tilesets and tiles is done when the tile cache is full and a tile that has started loading is no longer needed - so aborting is correct. Both tiles and internal tilesets are aborted if needed. So this isn't a bug in the sense that it will cause any problems but I agree the error log is not desired. It looks like the thrown abort signal error isn't being caught in one of the fetch promises causing it to print.

If you'd like to investigate and make a PR we can get it merged. Otherwise I'll have to take a look when I get a chance.

from 3dtilesrendererjs.

I just look a brief look at the TilesRenderer class and it's possible that this is the promise path where the abort is not getting caught: https://github.com/NASA-AMMOS/3DTilesRendererJS/blob/master/src/three/TilesRenderer.js#L341-L363

It's possible that just adding an empty "catch" statement to that promise chain will prevent the log if you'd like to give that a try.

from 3dtilesrendererjs.