https://bugs.documentfoundation.org/show_bug.cgi?id=173462
--- Comment #6 from ady <[email protected]> --- Whether the behavior described in this report can be reproduced or not, I'd like to point out that there are pros and cons for both cases, but their weight is not equal. A user could easily leave LO open until the clipboard gets pasted elsewhere, and only then close LO. IOW, a simple workaround exists. Now, let's imagine the other case, i.e. the clipboard keeps whatever was copied from within LO after LO was closed. This can easily be any time LO is closed, as copying data to the clipboard is probably one of the most common actions users perform. The user might not be interested in using that copied data again, but the clipboard would still be using memory in order to keep that data. We could even assume that, most often that not, after closing LO the user would not be using that copied data again. This means that, more often than not, the user would have less resources available, because part of those resources are occupied by data that is no longer needed. Considering that the user has control over when to close LO (e.g. after the copied data was pasted elsewhere), I would be in favor of releasing resources (e.g. the memory being used by the clipboard) so they are available. If this is the current behavior, please leave it as-is. If the behavior is/were to keep the clipboard occupied / used, then the user would need to be aware that he has to release it, manually (for example, by copying something else). The clipboard could be using a lot of memory, depending on what exactly was copied from LO. Leaving a meaningful amount of resources unavailable for the user / OS after LO was completely closed (and the data is not expected to be used again) would not be a positive behavior. If you need to use the copied data in order to paste it elsewhere, just paste the data and only then close LO. -- You are receiving this mail because: You are the assignee for the bug.
