Bug 98340 - Crashes when working on tables
Summary: Crashes when working on tables
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.1.0.3 release
Hardware: x86 (IA32) Linux (All)
: high major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-02 09:44 UTC by GAlcidesS
Modified: 2017-05-31 10:46 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
Crash report (11.95 KB, image/png)
2016-03-03 09:37 UTC, GAlcidesS
Details
Crashing table (7.13 KB, application/vnd.oasis.opendocument.text)
2016-03-03 10:57 UTC, GAlcidesS
Details
Crashing table (16.33 KB, application/vnd.oasis.opendocument.text)
2016-10-10 15:09 UTC, GAlcidesS
Details

Note You need to log in before you can comment on or make changes to this bug.
Description GAlcidesS 2016-03-02 09:44:04 UTC
There is no way to work on tables, Writer crashes every time I: try to copy and/or paste content, insert or delete a row, press ENTER to get a new line, delete or move a table, merge cells... summarizing, tables are not working at all.

Interestingly, they work when you create them, but after the 3rd time you open the file it crashes and keeps crashing.

I've read it is related to Java, antialising or two more reasons, but I've changed all of them without success.
Comment 1 Joel Madero 2016-03-02 19:03:37 UTC
Hi GAIcidesS,

We'll need a better description (reproducible steps) as to what is going on + a sample document. Please give us *exact* steps as to how to reproduce the problem - for example:

"copy/paste content" - what content? From what to what?

Marking as NEEDINFO - please provide the steps and a simple test document and then mark as UNCONFIRMED. Thanks!
Comment 2 GAlcidesS 2016-03-03 08:25:28 UTC
Hi. 
I can't attach a file as it will work the first three times, and then it will crash. Unfortunately, the table I'm working on has unpublished data that I have to keep for the moment.
However, I can give a description of the problem.

It started in the previous version of LibreOffice. Trying to solve it I installed the latest released version, but the problem still exists. After try and error with the possible crashing's origin, I tried something else, that original file had text and tables, so I split it: text & tables.
The text file works perfect, so did the tables' file the first two times I modified it, but then, crashed. Since the text file is flawless, it definitely  has to be the a table issue. Speaking of which, one time I opened the file and a comment box was created next to the table with the text "Segmentation!!!"; I think that is the explanation for this issue.
My guess is that during codification when saving the document, tables are badly coded and this segmentation issue appears.
I tried a second trick, I created a new table, smaller and I had the same result, three times after edition and crashing again.
Moreover, when opened in another office suite, additional cells in random raws on the right side appear with no reason. Also, merged cells are duplicated in additional columns that weren't there in the original file, so my idea of something going wrong when saving is supported.

The *exact* steps for the different crashing moments, regardless of the table content, would be:
Given a table:
Copy and paste the contents of one row in to another
Add rows above/below
Copy and paste text from the clipboard into one cell
Break the table 

When the program crashes I get a message saying that due to an error Libreoffice closed unexpectedly, that the changes will be saved, but when re-entering the file, the program was unable to save the latest version, so the original file was recovered instead. Sometimes the message says something about insufficient memory (??).

I made an update yesterday and I just tried to replicate the crashing, no success on that, hopefully is solved?? I'll update if the problem persists.

PS. I don't know how to mark as UNCONFIRMED
Comment 3 GAlcidesS 2016-03-03 09:37:45 UTC
Created attachment 123186 [details]
Crash report

I talked to soon.
After 30min of working on the table and when merging to cells, it crashed.
Comment 4 GAlcidesS 2016-03-03 10:57:30 UTC
Created attachment 123191 [details]
Crashing table
Comment 5 GAlcidesS 2016-03-03 10:59:33 UTC
This is how the crashing table looks like.
Those nested cells and additional cells on the right side were not there in the original file, after saving and re-opening the file, voila, everything mixed up and crashing everytime.
Comment 6 Joel Madero 2016-03-03 16:01:23 UTC
I still don't see easy steps to reproduce....so you're saying this is the "original file" but then you say that "after saving . . . everything mixed up". So is the file before "everything mixed up" or after (before would be "the original file", after would not).

And you still haven't really said when it crashes. So just opening the file crashes LibreOffice every time?
Comment 7 GAlcidesS 2016-03-03 16:29:41 UTC
Sorry for the unclear information, this is the first time I report a bug and to be honest I have no idea how, as you can see.

The table is the file that was saved in the computer. I deleted the contents, but the layout you can see in totally different from the file I was working on, summary, after saving the file, close the program and re-open it, the result is that altered version I attached.

The program crashed when I tried to copy content or move it (cut/paste or just dragging it) to another cell. Or when trying to add rows/columns, even when merging cells.

It wouldn't be rare if you cannot reproduce the error as it is triggered by different sequences. I manage to solve it, somehow, by creating the tables in another office suite (FreeOffice), but they are altered when saved as .odt and opened with Writer. However, when saved as .doc the problem is gone, even when I open that .doc file in Writer.
Comment 8 Joel Madero 2016-03-03 16:33:37 UTC
No need to apologize - this is a learning experience for everyone :)

I'll try to find some time today to download the file and mess around with it to try to repro the crash. It's too bad that we don't have the original (prior to the change after save as) but that's okay - not your fault at all.

Marking as UNCONFIRMED.
Comment 9 Buovjaga 2016-03-21 20:36:35 UTC
You can try getting a gdb trace of the crash: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information
Note you need to install the debug package first.

I did all the actions suggested, but could not get it to crash.

Arch Linux 64-bit, KDE Plasma 5
Version: 5.2.0.0.alpha0+
Build ID: 4bf2b6b2e6641c82e2b714e394482f1a1620b436
CPU Threads: 8; OS Version: Linux 4.4; UI Render: default; 
Locale: fi-FI (fi_FI.UTF-8)
Built on March 21st 2016
Comment 10 GAlcidesS 2016-03-22 08:50:32 UTC
Thanks for the time you spent.
The crashing file was apparently corrupt, I tried to open it today and Writer crashed even before opening it.
Regards.
Comment 11 arnaud.malfoy 2016-10-09 09:30:14 UTC
I tried to play around with the attached file:
-pasting content
-inserting one or more rows
-saving/reopening the file several time

I could not reproduce the bug. I'm on Ubuntu 16.04.1 &
Libre Office
Version: 5.2.2.2
Build ID: 8f96e87c890bf8fa77463cd4b640a2312823f3ad
CPU Threads: 4; OS Version: Linux 4.4; UI Render: default; 
Locale: en-US (en_US.UTF-8); Calc: group
Comment 12 GAlcidesS 2016-10-10 12:56:54 UTC
(In reply to arnaud.malfoy from comment #11)

Thanks for trying.
I keep experiencing the crashing problem but I narrowed the events to one common condition: tables adjusting to new sizes and across pages.
It was not the action of copy-pasting contents but the automatic adjustments the table suffers from these changes. For example, rows with different numbers of lines of content would have to split them, also a crash is expected when the font size changes and tables are adjusted, at least, that's my case. When recovered, the change appears successfully done.


Version: 5.1.5.2
Build ID: 7a864d8825610a8c07cfc3bc01dd4fce6a9447e5
CPU Threads: 4; OS Version: Linux 4.4; UI Render: default; 
Locale: en-US (en_US.UTF-8); Calc: group
Comment 13 arnaud.malfoy 2016-10-10 15:00:20 UTC
Could you explain step by step with detailed explanations what you do until it crashes. That will help us trying to reproduce the bug. Thanks a lot
Comment 14 GAlcidesS 2016-10-10 15:09:33 UTC
Created attachment 127927 [details]
Crashing table

See comment 14
Comment 15 GAlcidesS 2016-10-10 15:11:43 UTC
(In reply to arnaud.malfoy from comment #13)
> Could you explain step by step with detailed explanations what you do until
> it crashes. That will help us trying to reproduce the bug. Thanks a lot

Sure, I just made a new document (Attachment 127927 [details]) and made it crashed 3 times with these simple steps:

New document
line 1-> random text
insert table, 5 columns, 20 rows
Border box checked (only that one)
Copy random text inside the cells in no specific order, making the table bigger and expanding to more pages

-> FIRST CRASH

Reopen it (changes were saved) select the table 
Change the font size from 12 to 16

-> SECOND CRASH

Reopen it (changes are saved), select the table
Change the font size from 16 to 12

-> THIRD CRASH
Comment 16 Xisco Faulí 2016-10-10 16:17:51 UTC
Hi GAlcidesS,
Thank you for reporting this bug but I can't reproduce the crash following your steps in comment 15 in
Version: 5.3.0.0.alpha0+
Build ID: ae3ec79354f7b4967e736c6a4cd7c08fc52e2b7d
CPU Threads: 4; OS Version: Linux 4.2; UI Render: default; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group

Could you please provide a backtrace as mentioned in comment 9? On the other hand, have you tried to reset your profile* ?

* https://wiki.documentfoundation.org/UserProfile#GNU.2FLinux
Comment 17 GAlcidesS 2016-10-10 16:25:44 UTC
(In reply to Xisco Faulí from comment #16)

Interesting, you're not the only one who cannot reproduce the crash. I think I have a corrupted file or something.
Right now it's difficult for me to do the back trace (I'm busy in the next weeks), sorry. About the profile, yes and no. I saved my old profile (user folder) with a different name and ran the program with a brand new user folder, it crashed. Hence, I re-established my user as it was, keeps crashing.

Don't spend too much time on this, I appreciate your concern but although it's annoying, I can live with this for the moment, in the coming months I'll make a new installation and let you know.

Kind regards.

> Hi GAlcidesS,
> Thank you for reporting this bug but I can't reproduce the crash following
> your steps in comment 15 in
> Version: 5.3.0.0.alpha0+
> Build ID: ae3ec79354f7b4967e736c6a4cd7c08fc52e2b7d
> CPU Threads: 4; OS Version: Linux 4.2; UI Render: default; 
> Locale: ca-ES (ca_ES.UTF-8); Calc: group
> 
> Could you please provide a backtrace as mentioned in comment 9? On the other
> hand, have you tried to reset your profile* ?
> 
> * https://wiki.documentfoundation.org/UserProfile#GNU.2FLinux
Comment 18 QA Administrators 2017-05-02 11:37:13 UTC Comment hidden (obsolete)
Comment 19 QA Administrators 2017-05-31 10:46:37 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA 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

Warm Regards,
QA Team

MassPing-NeedInfo-20170531