Crash on closing SceneView with child node

[Jessewb786]

I have a view that shows a model:

val engine = rememberEngine()
val modelLoader = rememberModelLoader(engine)
val materialLoader = rememberMaterialLoader(engine)
Scene(
    modifier = Modifier
        .fillMaxSize(),
    engine = engine,
    modelLoader = modelLoader,
    view = rememberView(engine) {
        SceneView.createView(engine).apply {
            setShadowingEnabled(true)
            ambientOcclusionOptions.enabled = true
        }
    },
    childNodes = rememberNodes {
        add(
            element = ModelNode(
                modelInstance = modelLoader.createModelInstance(R.raw.part),
                scaleToUnits = 0.5f,
                centerOrigin = Position(x = 0.0f, y = -0.5f, z = 0.0f)
            ).apply {
                rotation = Rotation(y = -45f)
                renderableNodes.forEach { node ->
                    node.setMaterialInstances(
                        materialInstance = materialLoader.createColorInstance(Color.Gray)
                    )
                }
            }
        )
    },
    environment = rememberEnvironment(engine) {
        SceneView.createEnvironment(
            engine = engine,
            skybox = Skybox.Builder()
                .color(colorOf(rgb = 0.2f, a = 1.0f).toFloatArray())
                .build(engine)
        )
    }
)

When leaving, by default, this will crash with (Note that the crash does not happen is there is no childNode):

2024-04-01 16:47:13.097 32172-32172 Filament                E  in terminateAndDestroy:929
                                                               reason: Object <no-rtti> at 0xb4000077109fb500 doesn't exist (double free?)
2024-04-01 16:47:13.097 32172-32172 Filament                E  
2024-04-01 16:47:13.108 32172-32172 Sceneview               D  Engine destroyed

As a workaround, I override the original Scene method to do the following which solves the crash:

onRelease = { sceneView ->
    sceneView.childNodes = emptyList()
    sceneView.destroy()
}

It appears that there could be a second destroy somewhere that is leading to this crash.

[ThomasGorisse]

Reopen if it's still the case in v2.2.0

[NikitaGvozdilko]

@ThomasGorisse It still exists in v2.2.0
Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)

It is fixed for first 2-3 navigations, but then it crashed again.