Component used: androidx.lifecycle:lifecycle-viewmodel

Version used: 2.6.1

Devices/Android versions reproduced on: n/a

Current implementation of addCloseable doesn't have a check of mCleared, unlike of putTagIfAbsent. It may lead to memory leaks, because user can not add check of mCleared and close Closeable by its own. For example, if we start background task (thread, coroutine, rx-java chain), it is possible for this task to be active after onClear invocation (even this time is small) and add Closeable object after onClear. In this case, Closeable.close() will not be invoked.

Could be this check added to addCloseable implementation?