https://bz.apache.org/ooo/show_bug.cgi?id=126869
Issue ID: 126869
Issue Type: TASK
Summary: Analysis Task: Lost/Corrupted Documents after
Save/Shutdown
Product: General
Version: 3.4.0
Hardware: All
OS: All
Status: CONFIRMED
Severity: Normal
Priority: P5 (lowest)
Component: code
Assignee: [email protected]
Reporter: [email protected]
This meta-task is a subtask of Issue 126846 on Major Recurring Data/Operation
Loss/Corruption situations. See that issue for general context and an
attachment that provides details about the range of cases.
FOCUS
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.
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. (The consequences can be just as awful, but the causes are presumed to
be different.)
Although 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.
With regard to application freezing, this may result in there being no usable
document when shutdown has to be forced. There may be some relief for those
cases with measures that reduce document loss/corruption incidents.
There are likely to be very simple mitigations and remedies that can be
introduced in stages toward more complete solutions. That is to avoid
destabilizing the software with changes we introduce. Changes must be
reversible until we have confidence in them.
RELATED MATERIAL
Comment 3 of Issue 126846 applies to this task:
https://bz.apache.org/ooo/show_bug.cgi?id=126846#c3
Item (2) of Attachment 85292 of Issue 126846 applies to this task.
Item (1) of Attachment 85292, about all text being replaced by "#" characters,
is likely to be a bug of different origin. This occurs in a different manner
in which there is no corruption in the saved file -- it is complete and valid.
The "#" characters are actually there. This is an extreme case where what
appears to have been saved is different than what was actually saved only to be
discovered on subsequent opening of the saved file. The file is valid and
completely produced, although not what was though to be saved. Such cases need
to be considered separately.
EXISTING REPORTS
Attachment 85292 lists several Community Forum threads.
There are also bugzilla issues on incidents of damaged files that cannot be
opened because they are not a valid saved document.
Some of those will be marked as duplicates of this issue simply as a way to
provide cross-referencing.
--
You are receiving this mail because:
You are the assignee for the issue.
