Issue 128124 - Data corruption on Windows 10 when system is under load
Summary: Data corruption on Windows 10 when system is under load
Status: CLOSED DUPLICATE of issue 126869
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: 4.1.6
Hardware: All Windows 10
: P5 (lowest) Critical with 2 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2019-06-05 21:14 UTC by William Gathoye
Modified: 2019-06-05 22:52 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description William Gathoye 2019-06-05 21:14:57 UTC
Hello everyone,

This is the second time this week we are trying to help one of the unlucky Apache Open Office user running AOO on Windows 10.

When the system is under load, which happens to be nearly always the case with Windows installs belonging to non tech savvy users, AOO is becoming unresponsive and when the user is trying to save, the data appears saved but the file is filled with a bunch of hashtags (#####) which happens to be garbage data. The data is basically lost.

But, luckily, sometimes, there is a .tmp folder in %AppData%/TEMP/ folder. According from my understaning this could be some sort of coredump data, and sometime the file present in it is basically the file that has been lost. You just need to add a proper .odt extension and the file can be recovered.

While we have been able to reproduce the unresponsiveness of the program and the data corruption when the Windows 10 system is under load, we haven't been able to locate a .tmp folder in the TEMP directory structure in every case.

Due to the nature of this bug, I shall encourage your team to have a look at it with some more attention, especially as it is becoming quite frequent now (the second time this week we got the mention of this on Twitter).
Comment 1 Keith N. McKenna 2019-06-05 22:52:11 UTC
Previously reported multiple times. Please see issue 126896 and its parent issue for a greater discussion.

*** This issue has been marked as a duplicate of issue 126869 ***