#47 Node running after failed configInit of pipe

[Daniel Nachbaur]

If the one & only pipe on the node returns false after configInit(), the pipe thread gets destroyed, but the node is still alive and firing frames although there are no pipes on the node anymore

[Stefan Eilemann]

Works as designed. Failed resources are not deactivated, therefore the parent node is still active and running. It might still perform stuff like distributed computation.

Normally the impact should be minimal, since the node has never rendered and therefore never mapped scene data.

Imo the proper way would be to allow Node::configInit to also return false if a pipe init failed - app logic, since it does not want to keep the node alive. Today this is not possible since the pipe init does not start before the node init has finished.

What are you sinking? ;)

[Stefan Eilemann]

Reclassify as feature.

[Stefan Eilemann]

Set to pending, will close if no new insight.