soffice.bin crashed with SIGSEGV in std::_Hashtable<SfxPoolItem*, std::pair<SfxPoolItem* const, unsigned int>, std::allocator<std::pair<SfxPoolItem* const, unsigned int> >, std::__detail::_Select1st, std::equal_to<SfxPoolItem*>, std::hash<SfxPoolItem*>, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits<false, false, true> >::find()

Bug #1503478 reported by Alexandru Panoiu
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libreoffice (Ubuntu)
New
Undecided
Unassigned

Bug Description

This bug is quite strange. It occurred when I closed LibreOffice Write. Initially everything seemed just fine, but after a few seconds the system bug reporter popped up informing me that an internal error had occurred and urging me to report a bug. Well, I have reported it. I may add that LibreOffice seems to have certain tendency to crash upon closing, either by clicking the orange x or by choosing File > Quit.

$ lsb_release -rd
Description: Ubuntu Wily Werewolf (development branch)
Release: 15.10
$ apt-cache policy libreoffice-writer
libreoffice-writer:
  Installed: 1:5.0.2-0ubuntu1
  Candidate: 1:5.0.2-0ubuntu1
  Version table:
 *** 1:5.0.2-0ubuntu1 0
        500 http://ro.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: libreoffice-core 1:5.0.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
Uname: Linux 4.2.0-14-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Wed Oct 7 02:52:21 2015
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationDate: Installed on 2015-10-06 (0 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --writer file:///home/username/Documents/Notes/Ultrissa.odt --splash-pipe=5
SegvAnalysis:
 Segfault happened at: 0x7fef4c994129: mov (%rdx,%rcx,8),%rbp
 PC (0x7fef4c994129) ok
 source "(%rdx,%rcx,8)" (0x500000002) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
 std::_Hashtable<SfxPoolItem*, std::pair<SfxPoolItem* const, unsigned int>, std::allocator<std::pair<SfxPoolItem* const, unsigned int> >, std::__detail::_Select1st, std::equal_to<SfxPoolItem*>, std::hash<SfxPoolItem*>, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits<false, false, true> >::find(SfxPoolItem* const&) () from /usr/lib/libreoffice/program/libmergedlo.so
 SfxItemPool::Remove(SfxPoolItem const&) () from /usr/lib/libreoffice/program/libmergedlo.so
 SfxItemSet::~SfxItemSet() () from /usr/lib/libreoffice/program/libmergedlo.so
 SwFormat::~SwFormat() () from /usr/lib/libreoffice/program/../program/libswlo.so
 SwFrameFormat::~SwFrameFormat() () from /usr/lib/libreoffice/program/../program/libswlo.so
Title: soffice.bin crashed with SIGSEGV in std::_Hashtable<SfxPoolItem*, std::pair<SfxPoolItem* const, unsigned int>, std::allocator<std::pair<SfxPoolItem* const, unsigned int> >, std::__detail::_Select1st, std::equal_to<SfxPoolItem*>, std::hash<SfxPoolItem*>, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits<false, false, true> >::find()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Alexandru Panoiu (alexandru-panoiu) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1496500, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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