Lets reiterate the current status: - This only happens on an machine under heavy load with data on ecryptfs - the stacktrace show: a) this to happen at various locations (the stacktraces are different). b) even more important: some of the stacktraces show things, that cant possibly be, if the underlying system works correct. See the linked upstream discussion of this between me and Caolán McNamara. Quote: "The bug report's stack is from svx autocorrect, which means that ucbhelper::cancelCommandExecution and cppu::throwException have successfully thrown exceptions at least a hundred times or so before the crash, so its not the case that it's e.g. the first throw or two through the uno bridge." this means that the following: "With an eip of 0x100000 (in the i386 bug reports) meaning the call goes into nirvana." cant really happen unless there is some serious memory corruption around (or the stacktraces themselves are wrong, however in general, they look sane). The eip == 0x100000 is in a lot of stacktraces here while it should be a random (and different) number (pointing to the created ExceptionThrower object) instead.
As of now, there is _no_ indication that Libreoffice itself is at fault. it might demonstrate the problem more clearly, because: a) it is such a big project. b) such crashers appear to be random noise in other projects. @penalvch: I am not very happy about the setting of the bug state to confirmed again without discussion. My change was quite intentional given the above evidence. At least it needs to be set back to "Incomplete" until something shows Libreoffice to be at fault in this IMHO. To prevent a bug-state-war I will ask bugcontrol to have a look at it and leave state as is for now. -- 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: Invalid Status in “ecryptfs-utils” package in Ubuntu: Confirmed 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
