Double check if there are no memory leaks or any performance hogs

[MrCsabaToth]

I wonder if this is some possible memory leak or similar bug. Things to check:

• Verify that surface creation is executed once and GPS array is populated only once, no duplicates:

  recycling-trashcan-armap/app/src/main/java/dev/csaba/armap/recyclingtrashcans/TrashcanGeoRenderer.kt

  Line 102 in 24ce063

  for (location in locations) {

• Verify that we create the set of anchors and markers only once:

  recycling-trashcan-armap/app/src/main/java/dev/csaba/armap/recyclingtrashcans/TrashcanGeoRenderer.kt

  Line 227 in 24ce063

  val shouldAddAnchors = earthAnchors.isEmpty()

• Verify that during rendering

  recycling-trashcan-armap/app/src/main/java/dev/csaba/armap/recyclingtrashcans/TrashcanGeoRenderer.kt

  Line 263 in 24ce063

  private fun SampleRender.renderObjectAtAnchor(anchor: Anchor, index: Int) {

  there's no memory leak
• Possibly there's no memory leak in the support / helper code https://github.com/RecyclingTrashCans/recycling-trashcan-armap/tree/main/app/src/main/java/dev/csaba/armap/common

[MrCsabaToth]

Ref google-ar#11
Demo videos https://youtu.be/w3dUH4fB68Y and https://youtu.be/pXJcbjEno_0

[MrCsabaToth]

The new version's 3D objects has way less vertex count (very rectangular arrow), so hopefully that'll help the 3D engine.

[MrCsabaToth]

The release version worked very smoothly on the Nord (although not in 100F heat, but screen recording was on still). So I repurpose this ticket.