← Back to team overview

desktop-packages team mailing list archive

[Bug 745836] Re: soffice.bin crashed with SIGSEGV in cppu::throwException()

 

Success! I can easily and quickly reproduce the problem in Natty. It
isn't a time-related issue at all, simply resource-related.

Setup:
On Virtualbox 4.1.2, create a 32-bit Ubuntu VM with low memory (472MB in my case). Make sure your virtual hard-drive is at least 12GB so that Ubuntu allocates enough swap space to pull this off.
Install 11.04 from CD and install all updates, then reboot.
Vista-32 host if that makes any difference (which I doubt).

Steps to reproduce:
Open up LO writer, type a few words and save the file to disk. Leave the doc open, but minimized or otherwise inactive.
Open up every other app you can think of. System Monitor reported >200MB swapped for me.
Go back to LO and type a mis-spelled word, followed by a space.
Wait until the disk stops churning.
LO has crashed with this bug.

Once set up, it takes me less than ten minutes to produce another
instance.

I stayed on the safe side and tried to replicate the most extreme of all
reported conditions. It's likely that some of the steps I list are not
actually required to reproduce this, but narrowing it down will take
time.

I am currently upgrading the VM to oneiric to determine whether or not
this is still an issue there.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/745836

Title:
  soffice.bin crashed with SIGSEGV in cppu::throwException()

Status in LibreOffice Productivity Suite:
  New
Status in “libreoffice” package in Ubuntu:
  Confirmed
Status in “openoffice.org” package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: libreoffice

  1) lsb_release -rd
  Description:	Ubuntu 11.04
  Release:	11.04

  2) apt-cache policy libreoffice-calc
  libreoffice-calc:
    Installed: 1:3.3.3-1ubuntu2
    Candidate: 1:3.3.3-1ubuntu2
    Version table:
   *** 1:3.3.3-1ubuntu2 0
          100 /var/lib/dpkg/status
       1:3.3.2-1ubuntu5 0
          500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages
       1:3.3.2-1ubuntu4 0
          500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  apt-cache policy libreoffice-writer
  libreoffice-writer:
    Installed: 1:3.3.3-1ubuntu2
    Candidate: 1:3.3.3-1ubuntu2
    Version table:
   *** 1:3.3.3-1ubuntu2 0
          100 /var/lib/dpkg/status
       1:3.3.2-1ubuntu5 0
          500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages
       1:3.3.2-1ubuntu4 0
          500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  3) What is expected to happen in a KDE Natty in a KDE session with the
  KDE integration active or GNOME is a Writer or Calc file untouched for
  a long period of time (ex. 1 hour+) is when one tries to edit it, the
  application does not crash.

  4) What happens instead is it crashes. This is highly correlated to
  both EcryptfsInUse and resource constrained (Memory & CPU >> 50%)
  environments. Occurs with:

  + Intel drivers, Compiz not enabled, Writer open only bug 745836
  + binary ATI drivers, Compiz enabled, Calc open only bug 799047

  WORKAROUND: Use Gnumeric.

  apt-cache policy gnumeric
  gnumeric:
    Installed: 1.10.13-1ubuntu1
    Candidate: 1.10.13-1ubuntu1
    Version table:
   *** 1.10.13-1ubuntu1 0
          500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages
          100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: libreoffice-core 1:3.3.2-1ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
  Uname: Linux 2.6.38-7-generic i686
  Architecture: i386
  Date: Wed Mar 30 12:34:39 2011
  Disassembly: => 0x100000:	Cannot access memory at address 0x100000
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin -writer -splash-pipe=5
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x100000:	Cannot access memory at address 0x100000
   PC (0x00100000) not located in a known VMA region (needed executable region)!
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   ?? ()
   cppu::throwException(com::sun::star::uno::Any const&) () from /usr/lib/libreoffice/program/../basis-link/program/../ure-link/lib/libuno_cppuhelpergcc3.so.3
   ucbhelper::cancelCommandExecution(com::sun::star::ucb::IOErrorCode, com::sun::star::uno::Sequence<com::sun::star::uno::Any> const&, com::sun::star::uno::Reference<com::sun::star::ucb::XCommandEnvironment> const&, rtl::OUString const&, com::sun::star::uno::Reference<com::sun::star::ucb::XCommandProcessor> const&) () from /usr/lib/libreoffice/program/../basis-link/program/libucbhelper4gcc3.so
   ?? () from /usr/lib/libreoffice/program/../basis-link/program/libucpfile1.so
   ?? () from /usr/lib/libreoffice/program/../basis-link/program/libucpfile1.so
  Title: soffice.bin crashed with SIGSEGV in cppu::throwException()
  UpgradeStatus: Upgraded to natty on 2011-03-29 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/745836/+subscriptions