Memory leaks are preferable so as not to slow down

Question

Chrome Documentation:

NOTE. Both Singleton and base :: LazyInstance provide "leaky" traits for a global leak at shutdown. This is often recommended (with the possible exception, in library code, where the code can be dynamically loaded into another process address space or when data needs to be cleared when the process ends) so as not to slow down the work.

In this case, is this acceptable?

Answer 1

"" , . , , , ( Chromium, : - ).

, , , . , . , singleton - , .

, , .

, . , , .

, , , , . , .

. , , , , , , , , "". YMMV.

, , , . , Chromium , , , . , .

, , , , .

, , , ( , , ).

, ( , ). (ex: ). ( - , , ).

( ) , , , , (, dylib).

( ), ( , ), , , , , . , , , . , , , , .

, "" . . , , , .

Answer 2

( ) . , Linux-, .