NASA-AMMOS / NASA-AMMOS/3DTilesRendererJS
TilesRenderer: Load order can result in children loading first, taking LRUCache space before parents
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.5k
- Forks
- 416
- Avg merge
- 17h 52m
- Merged PRs (30d)
- 37
Description
This can be an issue when the renderer settings trigger tiles to load that immediately overflow the cache (as happens with #1065). This can result in a case where children are loaded but the parents are not. We may need to adjust the cache eviction approach to eject tiles that should be loaded with lower priority to ensure this inconsistency is avoided.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the cache-overflow scenario described here and in issue #1065, focusing on how renderer settings cause children to load before parents. Trace the LRUCache eviction path and determine how tile loading priority is represented. Done means the cache no longer retains children while their required parents are absent, with a regression test covering the load order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, three.js
- Domain
- computer-graphics, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100