Bug 80762 - EDITING: Spreadsheet crashes after inserting diagrams
Summary: EDITING: Spreadsheet crashes after inserting diagrams
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.2.5.2 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-01 16:46 UTC by MRPI
Modified: 2015-04-01 14:51 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description MRPI 2014-07-01 16:46:39 UTC
Problem description: 
All office versions reproducible crash at the attempt to save a spreadsheet if there has been some editing after inserting a new diagram into a spreadsheet with -lets say- six or more diagrams with each containing 3000 lines times 3 rows of data.

Steps to reproduce:
1. spreadsheet with 3000 lines and 100 colums of data
2. create XY diagrams from 3000 lines (X) with 3 columns each
3. copy and paste one of those diagrams
4. double-click diagram, edit, or edit something elsewhere
5. click on spreadsheet (leave diagram)
6. click save

Current behavior:
as described

Expected behavior:
should save without crashing
              
Operating System: Windows 7
Version: 4.2.5.2 release
Comment 1 tommy27 2014-07-17 19:31:07 UTC
please uplaod a test file

you could stop the sequence at step 3 than save and upload here that file to see if step 4 and 5 are reproducible
Comment 2 Joel Madero 2014-07-21 17:10:33 UTC
We need a test file - QA and developers can't be expected to create a fresh file with 3000 lines and 100 columns of data nor create diagrams. Also it's always best to use a file that you've already confirmed crashes so we are 100% sure that it's the same issue.

Marking as NEEDINFO - once you attach a file please mark as UNCONFIRMED. Thanks!
Comment 3 QA Administrators 2015-02-19 04:33:00 UTC
Dear Bug Submitter,

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

Message generated on: 2015-02-18
Comment 4 QA Administrators 2015-04-01 14:51:36 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 our bug tracker

-- The LibreOffice QA Team This NEEDINFO Message was generated on: 2015-04-01

Warm Regards,
QA Team