Issue 2716 - Recording Changes Results in Crash and Data Corruption
Summary: Recording Changes Results in Crash and Data Corruption
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: 641
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: yositune
QA Contact: issues@sw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-01-07 01:34 UTC by yositune
Modified: 2003-09-08 16:56 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description yositune 2002-01-07 01:34:15 UTC 
After editing a file for several days (alright more than a week...) and tracking
changes, program crashed and data file was corrupted and lost all but the first
two days of edits.

I did not QA how many tracked edits induced (if in fact it did|does) the error.

I have the file but it's protected and can't post it generally.  I will email
the file on request.  Thanks!
Comment 1 stefan.baltzer 2002-01-15 17:25:33 UTC 
Please email the file to me: Stefan.Baltzer@sun.com
Thank you.
Comment 2 stefan.baltzer 2002-06-05 15:40:00 UTC 
We recently fixed a bug (internal ID=95442) that lead to a crash when
doing undo after inserting a file into a document with "Record
changes" active.
Can you please comment if this was your problem? If so, it should not
occur in oo.org 642 any more. Please comment.
Comment 3 stefan.baltzer 2002-08-07 12:22:25 UTC 
Please check in the latest build. Then: 
a - close this issue if not reproducible
b - comment and reassign it to me if you can reproduce it.
Thank you.
Reassigned to submnitter.
Comment 4 yositune 2002-08-30 12:51:12 UTC 
Thanks Stefan.

From January until July I was doing my admissions to the attorney
professional bar and have been busy.. but you can call me Esquire now.. :)

I'll check this again.  I will try to track down the file I reported
the trouble with.
Comment 5 michael.bemmer 2003-03-24 11:57:04 UTC 
Despite some reminders there is still no target milestone asigned. From the fact
that reporter and owner are identical we conclude information is missing that
doesn't allow working on this issue. That's why we've decided to close such
issues. This is done without invidually taking care of each issue. If you feel
this decision has been wrong regarding this specific issue, please re-open it.
Comment 6 michael.bemmer 2003-03-24 12:03:31 UTC 
Despite some reminders there is still no target milestone asigned. From the fact
that reporter and owner are identical we conclude information is missing that
doesn't allow working on this issue. That's why we've decided to close such
issues. This is done without invidually taking care of each issue. If you feel
this decision has been wrong regarding this specific issue, please re-open it.
Comment 7 michael.bemmer 2003-03-24 12:11:12 UTC 
Despite some reminders there is still no target milestone asigned. From the fact
that reporter and owner are identical we conclude information is missing that
doesn't allow working on this issue. That's why we've decided to close such
issues. This is done without invidually taking care of each issue. If you feel
this decision has been wrong regarding this specific issue, please re-open it.