Bug 61661

Summary:	: Send causes crash
Product:	LibreOffice	Reporter:	jonnjones
Component:	Writer	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	serval2412
Priority:	medium
Version:	4.0.0.3 release
Hardware:	Other
OS:	Linux (All)
Whiteboard:	BSA target:4.0.1
Crash report or crash signature:		Regression By:
Attachments:	gdb and strace logs gdb run, but with backtrace this time

Description jonnjones 2013-03-01 12:27:21 UTC

Problem description: 
Just going to File->Send freezes and crashes libre office writer.

Steps to reproduce:
1. File
2. Send > [Nothing at all appears]
3. [Freeze and Crash]

Current behavior: 

Freezes and crashes libre office writer. The document recovery system appears when restarting libre office, with the document with which the crash happened. The same thing happens on multiple systems with different versions of Slackware, and different documents. Terminal output (sometimes not present):

GC Warning: Repeated allocation of very large block (appr. size 131072):
	May lead to memory leak and poor performance.
GC Warning: Repeated allocation of very large block (appr. size 258048):
	May lead to memory leak and poor performance.

GC Warning: Repeated allocation of very large block (appr. size 1024000):
	May lead to memory leak and poor performance.
GC Warning: Repeated allocation of very large block (appr. size 1024000):
	May lead to memory leak and poor performance.

Expected behavior:

Send, I suppose to mail? or other? At least not crash.
Operating System: Linux (Other)
Version: 4.0.0.3 release

Comment 1 Brenda Granados 2013-03-01 22:22:24 UTC

Hi, I cannot confirm this. I know Linux platforms can vary greatly, so maybe someone else can confirm this behavior.

I tested this on Ubuntu Linux x64.

Version: 4.0.0.3

Comment 2 Julien Nabet 2013-03-02 06:09:02 UTC

jonnjones: could you rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile) and test again?
Also, for the test, does it happen with a brand new odt file just containing "test"?

Finally, if you still reproduce this, could you try to retrieve a backtrace by following this link? (see https://wiki.documentfoundation.org/BugReport#How_to_get_a_backtrace_on_Linux)

Comment 3 jonnjones 2013-03-04 14:12:04 UTC

Created attachment 75896 [details]
gdb and strace logs

I accidentally fixed (or more like worked around) the problem. I was probing around the LO options to find how to change the ruler units, and when I came across the integrated Java in LO, I disabled it. I removed all Java from my computer a few months ago due to too many vulnerabilities and instability issues popping up all the time. I didn't realize LO had Java integrated. Disabling Java in LO fixed the problem. The Send menu shows up correctly now.

As for the tests, renaming the profile directory did NOT help. Trying it on a new odt file did NOT help.

As for the backtrace, running 

soffice --backtrace

never really started soffice up. So instead, I used gdb on soffice.bin . The results are in the attachment strace_gdb.log . At line 54 starts the strace log, as well.

Comment 4 Julien Nabet 2013-03-08 12:25:46 UTC

(In reply to comment #3)
> I accidentally fixed (or more like worked around) the problem. I was probing
> around the LO options to find how to change the ruler units, and when I came
> across the integrated Java in LO, I disabled it. I removed all Java from my
> computer a few months ago due to too many vulnerabilities and instability
> issues popping up all the time. I didn't realize LO had Java integrated.
> Disabling Java in LO fixed the problem. The Send menu shows up correctly now.
Thank you for your feedback.
Java isn't integrated in LibreOffice. When you launch for the first time, it tries to detect Java installed.
What's your precise Java version?
Do you reproduce the problem if you enable again Java?
(BTW, I'm not a Java fan but vulnerabilites are above all in Java browser module part :-))

> As for the tests, renaming the profile directory did NOT help. Trying it on
> a new odt file did NOT help.
Weird renaming the profile directory did not help
> 
> As for the backtrace, running 
> 
> soffice --backtrace
We can see the segfault but not the bt. If you reproduce the problem, instead of "quit", could you type "bt" to retrieve the backtrace then "quit"?

Comment 5 jonnjones 2013-03-09 12:18:42 UTC

Created attachment 76216 [details]
gdb run, but with backtrace this time

Ah yes, there is GCC Java. In the release notes for LibreOffice 4.0.1 Final (2013-03-06): "If you run Linux, the GCJ Java variant has known issues with LibreOffice, we advise to e.g. use OpenJDK instead."

Java version: 
gcc-java-4.5.2-x86_64 
gcc-java-4.7.1-x86_64

Although in the LO options, it lists JRE from the Free Software Foundation, version 1.5.0 .

I DO reproduce the problem if I enable Java again.
I renamed the profile directories in .libreoffice (no longer used, I know) and in .config/libreoffice , and the problem persists.

Sorry about that. Didn't realize gdb had a specific backtrace option too. File is attached as gdb-with-backtrace.log .

After updating to LO-4.0.1.2 , the problem is solved. No more crashing.

Comment 6 Julien Nabet 2013-03-09 12:58:49 UTC

(In reply to comment #5)
... 
> After updating to LO-4.0.1.2 , the problem is solved. No more crashing.
Great! Thank you for your feedback. So I put this tracker to WFM + target 4.0.1 in whiteboard.