soffice.bin crashed with SIGSEGV in *__GI___libc_free()

Bug #645155 reported by Mikko Rantalainen
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
openoffice.org (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: openoffice.org

Looking at the stacktrace, this may be double free() somewhere.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: openoffice.org-core 1:3.2.0-7ubuntu4.1
ProcVersionSignature: Ubuntu 2.6.31-11.154-rt
Uname: Linux 2.6.31-11-rt x86_64
Architecture: amd64
CheckboxSubmission: f0bf0101e3df07a87acfbc156f0db03d
CheckboxSystem: b5acb6c9ca4017b1d44043910f45329d
Date: Wed Sep 22 15:02:58 2010
Disassembly: => 0x7f31c32fced9: Cannot access memory at address 0x7f31c32fced9
ExecutablePath: /usr/lib/openoffice/program/soffice.bin
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate amd64 (20091020.3)
ProcCmdline: /usr/lib/openoffice/program/soffice.bin -writer /tmp/webli_pedanet_interface_suggestion_v1.3.odt -splash-pipe=5
SegvAnalysis:
 Segfault happened at: 0x7f31c32fced9: Cannot access memory at address 0x7f31c32fced9
 PC (0x7f31c32fced9) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: openoffice.org
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 *__GI___libc_free (mem=<value optimized out>)
Title: soffice.bin crashed with SIGSEGV in *__GI___libc_free()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Mikko Rantalainen (mira) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 free () from /lib/libc.so.6

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Mikko Rantalainen (mira)
visibility: private → public
Revision history for this message
Rolf Leggewie (r0lf) wrote :

looks very similar to bug 627365. Does this happen in Maverick as well?

Changed in openoffice.org (Ubuntu):
assignee: nobody → Rolf Leggewie (r0lf)
status: New → Incomplete
Revision history for this message
João Pinto (joaopinto) wrote :

Most of the times I was able to reproduce the crash quitting oocal after starting it with:
oocalc "-accept=socket,host=localhost,port=8100;urp;StarOffice.ServiceManager" -norestore -nofirststartwizard -nologo

I didn't experienced it on Maverick yet.

Changed in openoffice.org (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Rolf Leggewie (r0lf) wrote :

well, the log and backtrace isn't really helpful. So, we need a sure-fire way to reproduce this to proceed. I can't set this ticket to confirmed with the little valuable data there currently is.

Changed in openoffice.org (Ubuntu):
assignee: Rolf Leggewie (r0lf) → nobody
status: Confirmed → Incomplete
Revision history for this message
João Pinto (joaopinto) wrote :

If you need to set it to incomplete then please provide instructions on what needs to be done to make it "complete".
Have you tried to reproduce the crash per my instructions on Lucid ?

Changed in openoffice.org (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Rolf Leggewie (r0lf) wrote :

I just came back to this ticket. Sorry, my bad, the status change was actually unintentional. Not sure, but maybe our messages crossed. I don't recall seeing your instructions for how you usually manage to reproduce this, for example.

FWIW, when I start oocalc the way you describe and then quit it, the program does not crash but it actually does not close, either.

Revision history for this message
penalvch (penalvch) wrote :

Mikko Rantalainen, thank you for reporting this bug and helping make Ubuntu better. This bug is unreproducible in Ubuntu 10.10 LibreOffice Calc at the Terminal:

localc "-accept=socket,host=localhost,port=8100;urp;StarOffice.ServiceManager" -norestore -nofirststartwizard -nologo

A blank Calc file opens with no crash. Does this work for you?

lsb_release -rd
Description: Ubuntu 10.10
Release: 10.10

sudo add-apt-repository ppa:libreoffice/ppa && sudo apt-get update && sudo apt-get -y upgrade && sudo apt-get -y install libreoffice-calc

 apt-cache policy libreoffice-calc
libreoffice-calc:
  Installed: 1:3.3.0-1maverick1
  Candidate: 1:3.3.0-1maverick1
  Version table:
 *** 1:3.3.0-1maverick1 0
        500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ maverick/main i386 Packages
        100 /var/lib/dpkg/status

Changed in openoffice.org (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for openoffice.org (Ubuntu) because there has been no activity for 60 days.]

Changed in openoffice.org (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.