soffice.bin crashed with SIGSEGV in JNI_CreateJavaVM()

[Márovics István]

For first launch it working for a while, but in next time it just not starting at all.

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
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 26 08:12:13 2017
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationDate: Installed on 2013-02-12 (1716 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3)
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --writer smb://dlink-a8cdb7/data/Docs/Jehova/GyulekezetiProgramok/Elerkezett_babilon_iteletenek_oraja_vazlat.odt --splash-pipe=5
SegvAnalysis:
 Segfault happened at: 0xa5ab5bc5: movb $0x0,(%eax)
 PC (0xa5ab5bc5) ok
 source "$0x0" ok
 destination "(%eax)" (0xbf6dcfe0) 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 (6 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

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 #1726145, 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.