Commenting on a document by two users gives a stack of comments. After removing the the first comment (not relevant anymore), but keeping the following comments, writer will crash more often than not. It does not crash immediately, but after a few seconds.
Would it be possible you attach the file so we can give it a try easily? Indeed, putting 2 comments in odt file is simple but not straighforward if we want to have comments of different users. You can use this link https://bugs.documentfoundation.org/attachment.cgi?bugid=101145&action=enter Beware, any attachment is automatically made public so remove any confidential/private part from it.
Created attachment 126429 [details] Reduced document with comments. Will crash on demand.
With LO Debian package 5.1.5.1, I don't reproduce the crash with the document. I tested with gtk3, gtk, gen and kde4 rendering. On which env are you? (MacOs, Linux, Windows) Could you rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile) and give a new try?
I work on Ubuntu 16.04 64 bits Libreoffice 5.1.4.2 Replacing the profile does not help. My college is working on windows 10 64 bits Libreoffice 5.1.4.2 The document is 200 pages. It crashes regular if we use comments. Adding, deleting and changing comments is very unstable in our situation. This has been so for the past two years, independent of the versions.
(In reply to Aron Boss from comment #4) > I work on Ubuntu 16.04 64 bits Libreoffice 5.1.4.2 > > Replacing the profile does not help. > > My college is working on windows 10 64 bits Libreoffice 5.1.4.2 > > The document is 200 pages. It crashes regular if we use comments. Adding, > deleting and changing comments is very unstable in our situation. > > This has been so for the past two years, independent of the versions. Ok but we need a detailed step by step process to reproduce the problem. Would it be possible you retrieve a backtrace? (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace)
Created attachment 126836 [details] trace log Document will crash on start with trace on
(In reply to Aron Boss from comment #6) > Created attachment 126836 [details] > trace log > > Document will crash on start with trace on You must type "c" (for "continue") to retrieve the right bt. Indeed, this one concerns Java part and is unrelated. Type "c" until there's no "?".
soffice --backtrace GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/lib/libreoffice/program/soffice.bin...(no debugging symbols found)...done. log will be saved as gdbtrace.log, this will take some time, patience... (soffice:9197): Gdk-WARNING **: gdk_window_set_icon_list: icons too large (soffice:9197): Gdk-WARNING **: gdk_window_set_icon_list: icons too large I will need a copy with symbols?
(In reply to Aron Boss from comment #8) > soffice --backtrace >... > I will need a copy with symbols? A copy with symbols is better because you'll get more detailed information. However the problem here is that the easy method (soffice --backtrace) won't be sufficient since it stops at first SIGSEGV which doesn't interest us here. So you can use alternative method indicated here https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace (end of paragraph) 1) Open 2 terminal/console. 2) On console 1: Launch LO as usual 3) On console 2: a) Launch gdb this way: "gdb --pid `pgrep soffice`" (without quotes but don't forget backquote) It'll take some time and will suspend LO. b) type "c" in console 2 so it will "unsuspend" LO 4) Reproduce the crash in LO 5) in LO, type "bt" if you see only "?" type "c" then "bt" again. At a moment, you'll get something else than only "?", it'll be the right bt. It can seem a bit complicated but once you'll do it some times, it'll be quick and easy.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20170131
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20170328