soffice.bin crashed with SIGSEGV in _expand_stack_to()

Bug #1726145 reported by Morten Kristoffer Hansen
88
This bug affects 12 people
Affects Status Importance Assigned to Milestone
libreoffice (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

LibreOffice crashed during startup. The splashscreen was visible for a sort period, then nothing.

This on a fresh upgrade to Ubuntu 17.10

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: libreoffice-core 1:5.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic i686
ApportVersion: 2.20.7-0ubuntu3
Architecture: i386
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 22 21:57:47 2017
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationDate: Installed on 2012-10-29 (1819 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --writer file:///tmp/mozilla_mkhansen0/SGH%20-%20Nyhedsbrev%209.%20%C3%A5rgang%20nr.%205%202017.docx
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=da_DK.UTF-8
 SHELL=/bin/bash
 LD_LIBRARY_PATH=<set>
SegvAnalysis:
 Segfault happened at: 0xa4e39bc5: movb $0x0,(%eax)
 PC (0xa4e39bc5) ok
 source "$0x0" ok
 destination "(%eax)" (0xbf224fe0) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
 ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
 ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
 ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
 ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
 JNI_CreateJavaVM () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
Title: soffice.bin crashed with SIGSEGV in JNI_CreateJavaVM()
UpgradeStatus: Upgraded to artful on 2017-10-19 (2 days ago)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo

Revision history for this message
Morten Kristoffer Hansen (mkhansen) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _expand_stack_to (bottom=0xbf224fff <error: Cannot access memory at address 0xbf224fff>, bottom@entry=0xbf224000 <error: Cannot access memory at address 0xbf224000>) at ./src/hotspot/src/os/linux/vm/os_linux.cpp:673
 os::Linux::manually_expand_stack (t=0x33dfc00, addr=0xbf224000 <error: Cannot access memory at address 0xbf224000>) at ./src/hotspot/src/os/linux/vm/os_linux.cpp:686
 os::create_attached_thread (thread=0x33dfc00) at ./src/hotspot/src/os/linux/vm/os_linux.cpp:965
 os::create_main_thread (thread=0x33dfc00) at ./src/hotspot/src/os/linux/vm/os_linux.cpp:915
 Thread::set_as_starting_thread (this=0x33dfc00) at ./src/hotspot/src/share/vm/runtime/thread.cpp:988

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
summary: - soffice.bin crashed with SIGSEGV in JNI_CreateJavaVM()
+ soffice.bin crashed with SIGSEGV in _expand_stack_to()
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
tags: added: bionic
Revision history for this message
Olivier Tilloy (osomon) wrote :

This is bug #1699772.

Revision history for this message
Olivier Tilloy (osomon) wrote :

Note to self: when checking for potential duplicates, ask bug reporters to check for the output of:

    grep enabled ~/.config/libreoffice/4/user/config/javasettings_Linux_*.xml

If it looks like:

    <enabled xsi:nil="true"/>

Ask them to edit that file with a text editor and change it to:

    <enabled xsi:nil="false">false</enabled>

And see if that makes the crash go away.

Olivier Tilloy (osomon)
information type: Private → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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