Clean shutdown

[Ichthyostega]

clean Application shutdown

this is a tracking ticket -- individual tasks depending.

Even while Lumiera is designed allowing simply to »pull the plug«, it is important to care for a super clean shutdown with zero leaks, races and suppressed exceptions. Because, usually, these are common symptoms of conceptual mismatches, which shouldn't be allowed to linger

[Christian Thäter]

Replying to ichthyo:

clean Application shutdown

this is a meta-ticket to keep track of relevant issues

Even while Lumiera is designed allowing simply to »pull the plug«, it is important to care for a super clean shutdown with zero leaks, races and suppressed exceptions. Because, usually, these are common symptoms of conceptual mismatches, which shouldn't be allowed to linger

Moreover I was thinking about different shutdown compiletime options. That is 'clean but slow' shutdown for ALPHA and BETA builds and a 'fast' shutdown for RELEASE builds. A lot objects don't really need to be deconstructed on shutdown but this is twofold and we need to prepare it in a way that the necessary actions are still guaranteed to be executed at fast shutdown (that likely implies a 2 or 3 stage shutdown for some classes, close eg: -> destroy -> free).

Further there is the 'resourcecollector' which manages emergency shutdowns, generally I want to be able to pull the plug at any time without loosing (much..) work. but even this can be done in multiple stages, writing as much data as possible out and syncing the log.

[Ichthyostega]

yeah, good point. I think, on a large extent, we are already kapable of doing so. Off the top of my head, I can't recall any dtor doing any state saving. Anyway, I'll add a separate ticket to track fast shutdown

[Undercover Agent]

Migration MasterTickets ⟼ Subtickets-plugin

[Ichthyostega]

• Add subticket #1416 (clarify lifecycle of the »Vessel«)
• in addition, also connect to #1146 (complete application startup sequence)