Bug 54899 - 2 open files contaminated
Summary: 2 open files contaminated
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: x86 (IA32) Windows (All)
: medium critical
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-14 02:03 UTC by realtimexxx
Modified: 2014-06-01 20:30 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Data that was cut out of contaminated file and pasted to a new file. (122.25 KB, application/vnd.oasis.opendocument.spreadsheet)
2012-09-14 02:03 UTC, realtimexxx
Details

Note You need to log in before you can comment on or make changes to this bug.
Description realtimexxx 2012-09-14 02:03:02 UTC
Created attachment 67135 [details]
Data that was cut out of contaminated file and pasted to a new file.

Contamination of 2 files that were open.  One was a spreadsheet and the other was a document.  A large part of the spreadsheet file became part of the document file.

Part of the data from the spreadsheet appeared as part of the document.  But the data from the spreadsheet had borders and anchors (if that is the correct term) and looks to me like it could be the border for a large picture.  

The files were quite large and were not created in a few days.

The only thing I can think of is that it must be some sort of memory management problem or virtual memory  problem.

I cut out the contaminated part and pasted it into a new file.
Comment 1 Sören 2012-12-29 19:31:19 UTC
After investigating the contends of the ODS-file it seems as if it contains the original table as embedded object, which also is editable. In the same way as what you get if you do Insert->Object->OLE Object->Create from file.
But as I don't know how it appeared here, I can't say if there is a bug. At least the resulting file seems to be well-structured (and the data in it can be extracted by copying)

My experiments where done in
Version 4.0.0.0.beta2 (Build ID: 4104d660979c57e1160b5135634f732918460a0)
on Ubuntu 12.04 (x86)
Comment 2 bfoman (inactive) 2013-03-22 10:05:40 UTC
(In reply to comment #0)
> Contamination of 2 files that were open.  One was a spreadsheet and the
> other was a document.  A large part of the spreadsheet file became part of
> the document file.

Is this bug reproducible? Without steps to reproduce this bug cannot be fixed.
Comment 3 tommy27 2013-08-26 12:59:06 UTC
setting status to NEEDINFO
Comment 4 QA Administrators 2014-05-17 00:34:37 UTC
Dear Bug Submitter,

Please read the entire message before proceeding.

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team
Comment 5 QA Administrators 2014-06-01 20:30:35 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO