soffice.bin crashed with SIGSEGV in std::list<Link, std::allocator<Link> >::remove()

Bug #1027043 reported by Gabriel Diosan
40
This bug affects 6 people
Affects Status Importance Assigned to Milestone
libreoffice (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Libreoffice (Impress) crashed while trying to close the application. Impress hung for a few moments and finally closed. Crash was picked up after Impress shutdown.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: libreoffice-core 1:3.6.0~rc2-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-5.5-generic 3.5.0-rc7
Uname: Linux 3.5.0-5-generic i686
ApportVersion: 2.4-0ubuntu3
Architecture: i386
Date: Fri Jul 20 19:21:06 2012
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120627)
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --impress --splash-pipe=6
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb6402fe7 <_ZNSt4listI4LinkSaIS0_EE6removeERKS0_+23>: mov (%eax),%edi
 PC (0xb6402fe7) ok
 source "(%eax)" (0x00000050) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
 std::list<Link, std::allocator<Link> >::remove(Link const&) () from /usr/lib/libreoffice/program/libvcllo.so
 VclEventListeners::removeListener(Link const&) () from /usr/lib/libreoffice/program/libvcllo.so
 Window::RemoveEventListener(Link const&) () from /usr/lib/libreoffice/program/libvcllo.so
 ?? () from /usr/lib/libreoffice/program/../program/libsdlo.so
 ?? () from /usr/lib/libreoffice/program/../program/libsdlo.so
Title: soffice.bin crashed with SIGSEGV in std::list<Link, std::allocator<Link> >::remove()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
 gnome-session[1482]: WARNING: Session 'ubuntu' runnable check failed: Exited with code 1
 gnome-session[1482]: WARNING: Error while executing session-migration: Failed to execute child process "session-migration" (No such file or directory)

Revision history for this message
Gabriel Diosan (gabsd84) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 std::list<Link, std::allocator<Link> >::remove (this=0x50, __value=...) at /build/buildd/libreoffice-3.6.0~rc2/vcl/source/app/vclevent.cxx:166
 VclEventListeners::removeListener (this=0x50, rListener=...) at /build/buildd/libreoffice-3.6.0~rc2/vcl/source/app/vclevent.cxx:114
 Window::RemoveEventListener (this=0x9740f40, rEventListener=...) at /build/buildd/libreoffice-3.6.0~rc2/vcl/source/window/window.cxx:5223
 sd::toolpanel::FocusManager::RemoveUnusedEventListener (this=0xae69b7e8, pWindow=0x9740f40) at /build/buildd/libreoffice-3.6.0~rc2/sd/source/ui/toolpanel/TaskPaneFocusManager.cxx:265
 sd::toolpanel::FocusManager::RemoveLinks (this=0xae69b7e8, pWindow=0x9d05590) at /build/buildd/libreoffice-3.6.0~rc2/sd/source/ui/toolpanel/TaskPaneFocusManager.cxx:242

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in libreoffice (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in libreoffice (Ubuntu):
status: New → Confirmed
Revision history for this message
Björn Michaelsen (bjoern-michaelsen) wrote :

C++11 regression a per https://lists.ubuntu.com/archives/ubuntu-devel/2012-June/035310.html ff. -- doesnt happen on precise.

Changed in libreoffice (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Gabriel Diosan (gabsd84) wrote :

The crash is still happening after upgrading to libreoffice 3.6.0~rc2-0ubuntu3

visibility: private → public
Revision history for this message
Björn Michaelsen (bjoern-michaelsen) wrote :

I just did an:

 apt-get purge ure && apt-get autoremove

installed these quantal binaries on precise with dpkg -i:

libboost-date-time1.49.0_1.49.0-3ubuntu1_amd64.deb
libcmis-0.2-2_0.2.3-1_amd64.deb
librdf0_1.0.15-1_amd64.deb
libreoffice-common_3.6.0~rc2-0ubuntu3_all.deb
libreoffice-core_3.6.0~rc2-0ubuntu3_amd64.deb
libreoffice-draw_3.6.0~rc2-0ubuntu3_amd64.deb
libreoffice-impress_3.6.0~rc2-0ubuntu3_amd64.deb
libreoffice-style-human_3.6.0~rc2-0ubuntu3_all(1).deb
libreoffice-style-human_3.6.0~rc2-0ubuntu3_all.deb
uno-libs3_3.6.0~rc2-0ubuntu3_amd64.deb
ure_3.6.0~rc2-0ubuntu3_amd64.deb

and the bug is *not* there. Thus these packages appear to be clean, and its gotta be from somewhere else in quantal.

Revision history for this message
Björn Michaelsen (bjoern-michaelsen) wrote :

hmmm, cant reproduce it on quantal i386 right now with a few tries.
Do you have a good reproduction scenario?

Revision history for this message
Gabriel Diosan (gabsd84) wrote :

The crash usually shows itself in Impress. It seems to happen less often in the other components.

To reproduce the crash I do the following:

1. Start Libreoffice Impress;
2. Make some changes and close Impress;
3. Click on Discard changes.

The crash does not happen every time. It usually happens 1 in every 10 or so times that you repeat this sequence.

Revision history for this message
Björn Michaelsen (bjoern-michaelsen) wrote :

ok, doing some change in the presentation was what I left out. Now I see it too -- and I even see in with those packages on precise.

Revision history for this message
Björn Michaelsen (bjoern-michaelsen) wrote :

Can not reproduce this anymore on LibreOffice 4.1 on Ubuntu 13.10, closing WORKSFORME.

Changed in libreoffice (Ubuntu):
status: Triaged → Fix Released
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.