You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've encountered a bug related to external tilesets. It appears that the tile somehow was aborted before. However, I have no idea how that's possible, considering an AbortController instance is created per each load. Therefore, at this point, I need to check additionally if the signal was aborted before (signal.aborted). It seems to happen randomly (but only if you have externals tilesets defined in the main Tileset.json).
{
"stack": "Error: signal is aborted without reason\n at http://localhost:3000/node_modules/3d-tiles-renderer/src/base/TilesRendererBase.js?v=02784ebd:439:19\n at LRUCache.unloadUnusedContent (http://localhost:3000/node_modules/3d-tiles-renderer/src/utilities/LRUCache.js?v=02784ebd:162:26)\n at http://localhost:3000/node_modules/3d-tiles-renderer/src/utilities/LRUCache.js?v=02784ebd:180:10"
}
Update: I'm unable to check the status of the variable signal.aborted
if (t.__loadAbort.signal.aborted === false)
t.__loadAbort.abort(); //Bypasses the if statement and throws an exception. What's going on?
The text was updated successfully, but these errors were encountered:
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.
I've encountered a bug related to external tilesets. It appears that the tile somehow was aborted before. However, I have no idea how that's possible, considering an AbortController instance is created per each load. Therefore, at this point, I need to check additionally if the signal was aborted before (
signal.aborted
). It seems to happen randomly (but only if you have externals tilesets defined in the main Tileset.json).Update: I'm unable to check the status of the variable
signal.aborted
The text was updated successfully, but these errors were encountered: