![]() That is to avoid destabilizing the software with changes we introduce. There are likely to be very simple mitigations and remedies that can be introduced in stages toward more complete solutions. There may be some relief for those cases with measures that reduce document loss/corruption incidents. ![]() With regard to application freezing, this may result in there being no usable document when shutdown has to be forced. (The consequences can be just as awful, but the causes are presumed to be different.)Īlthough there may be occasional connections, this task does not address application freezing, auto-recovery problems, decryption problems, locking issues and user-profile damage of the kind where certain functions cease working. This is about how AOO saves a file such that it is not valid, in contrast with a successful save of a valid document, but the content is altered in some manner. ![]() This task focuses on everything that is known and can be determined about incident where thought-to-be-saved documents are found to be corrupted and unusable on subsequent opening. See that issue for general context and an attachment that provides details about the range of cases. This meta-task is a subtask of Issue 126846 on Major Recurring Data/Operation Loss/Corruption situations. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |