CesiumGS / CesiumGS/cesium

expiredContent not destroy when tile.unloadContent is called

Open
#11,539 2 comments 0 reactions 0 assignees View on GitHub
category - 3d tiles category - traversal & selection type - bug
Dominant language
JavaScript
Stars
15.8k
Forks
3.9k
Avg merge
4d 6h
Merged PRs (30d)
34

Description

hi, I've find a problem when i used expiredContent in 3DTiles, an error occurs in the follow picture:
![Image](https://github.com/CesiumGS/cesium/assets/23093267/90b22a5d-12a9-4720-8949-0f1f5e260ad7)

and after debugger ( the following picture shows) to locate the reason, i've find that in the tile's unloadContent method, there maybe exists two kind of content at the same time, and it seems only destory the _content which in on processing state, leave another _expiredContent undestroyed.

![Image3](https://github.com/CesiumGS/cesium/assets/23093267/b5a42e88-308d-4e89-8b4c-5548289d4cf0)

I'm not sure it is a bug or the normal logic?

Contributor guide

Open the contributing guide

Research direction

Start at the 3D Tiles tile.unloadContent method and reproduce the expiredContent case described in the issue. Trace how _content and _expiredContent coexist during unloading, then verify that both are handled correctly without the reported error.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
computer-graphics
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.