[Libreoffice-qa] SIGSEV after clicking through different QuickStarter entries and closing it

[Thomas Hackert]

Hello @ll,
I found an interesting bug (I think ... ;) ) and I need someone, who 
could try it on his/her machine ... ;)

Steps to reproduce:
1. Start LO
2. Activate the QuickStarter ("Tools – Options – LibreOffice – 
Memory" on the right below "LibreOffice QuickStarter")
3. Press <Ctrl>+<Q> to close LO completely
4. Close the QuickStarter, if it is still open
5. Start LO via command prompt 
(/opt/libreoffice4.2/program/soffice). I used Konsole Version 2.11.3
and KDE 4.11.3, but it would be nice, if someone with a different 
desktop manager could try it as well ... ;)

The QuickStarter should be visible alongside LO's StartCenter

6. Close LO via <Ctrl>+<Q>
7. Click on the QuickStarter and open each item there ("Text 
Document", "Spreadsheet" etc.) and close it promptly without doing 
anything else.
8. Skip "Disable systray QuickStarter", but do not forget to open 
all other items ... ;)
9. Close the QuickStarter via "Exit QuickStarter"

On my system (Debian Testing AMD64 and LO with installed 
Germanophone lang- as well as helppack (Version: 4.2.0.2 Build ID: 
601a398b803303d1a40a3299729531824fe0db56) ) Java spits out the 
message

<quote>
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fad73ebdd54, pid=11928, 
tid=140382963963968
#
# JRE version: Java(TM) SE Runtime Environment (8.0-b118) (build 
1.8.0-ea-b118)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.0-b60 mixed mode 
linux-amd64 compressed oops)
# Problematic frame:
# C  [libpthread.so.0+0x9d54]  pthread_mutex_lock+0x4
#
# Failed to write core dump. Core dumps have been disabled. To 
enable core dumping, try "ulimit -c unlimited" before starting Java 
again
#
# An error report file with more information is saved as:
# ~./LO/hs_err_pid11928.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
#

[error occurred during error reporting , id 0xb]
</quote>

Would someone be so kind to try to reproduce it, please? Though it 
does not affect any work with LO (as far as I see, that is ... ;) ), 
but I am not sure, if it could have any further impact for our users 
... :(
Thanks for testing
Thomas.

-- 
BOFH excuse #11:
magnetic interference from money/credit cards