Steps to reproduce (1) Download file "DOC-export footnote Error.odt" attached to bug 73095 "Writer's UI crashes when scrolling pages if formatting marks are visible". (2) Open the file from the command line. The program presents the document window un-maximized as per first screenshot. Make sure that your screen shows the same amount of the document as mine does. (3) Type <page-down> 38 times. But when I was running under gdb, the behaviour was a bit different: (a) The window opened initially showing more of the document; I made the window less high accordingly. (b) It took 41 times <page-down> to reach the particular point in the document. Anyway, the document is now positioned as in the second screenshot. (4) Type <page-down>. The document is positioned as in the third screenshot. (5) Take menu options File > Close. SIGABRT. I do not observe the crash after a mere 38 <page-down>'s, but any larger number gives me a crash when I close the program. My LibreOffice is master commit 295bc87, fetched 2014-02-24 UTC, configured as: --enable-option-checking=fatal --enable-dbgutil --enable-crashdump --without-system-postgresql --without-myspell-dicts --with-extra-buildid --without-doxygen --with-external-tar=/home/terry/lo_hacking/git/src For comparison, I do not see the crash with LO version 4.2.0.1, but the "canary" pointer (all nines) evident in the backtrace makes me suspect that my debug build is a factor in causing the crash.
Created attachment 94947 [details] screenshot, document as first displayed
Created attachment 94948 [details] screenshot, document window after 38 times <page-down>
Created attachment 94949 [details] screenshot, document window after 39th <page-down>
Created attachment 94950 [details] typescript with backtrace with symbols
Setting status NEW.
Bugzilla search does not go into attachments, so let me note here that the backtrace shows STL debug objects near the top of the stack.
On pc Debian x86-64 with master sources updated today, I don't reproduce this. Could you give a try with a recent LO version?
Created attachment 115010 [details] typescript with segfault; backtrace is at line 400 The problem is now a segfault in master commit 69262e4, fetched 2014-04-15 21:42 UTC, configured --enable-option-checking=fatal --enable-dbgutil --enable-crashdump --without-system-postgresql --without-myspell-dicts --with-extra-buildid --without-doxygen --with-external-tar=/home/terry/lo_hacking/git/src --enable-online-update --disable-gstreamer-1-0 --enable-gstreamer-0-10 built and running on debian-wheezy. I have a different (smaller) display now, so needed more <page-down>'s and may not have gone exactly as far down the document as I did in 2014. I do not know whether this can account for different behaviour now. As before, "canary" pointer value all-nines in the frame at the top of the call stack suggests that only a debug build will show the problem in this particular way. The function names in frames 2 through 47 on the current backtrace are same as in frames 9 through 54 of the backtrace from 2014-03-02.
setting status NEW and changing "sigabrt" to "segfault" in summary.
Taking a look at some not recent bugs, I just noticed this: #6 0x00007f85a9697d86 in accessibility::AccessibleProxyEditSource_Impl::AccessibleProxyEditSource_Impl (this=0x3506920, rObj=..., rView=..., rViewWindow=...) at /home/terry/lo_hacking/git/libo2/svx/source/accessibility/AccessibleEmptyEditSource.cxx:179 Do you have accessibility options enabled? If yes, could you give a try after having disabled them?
I have reproduced a SIGABRT with two set of settings in "Tools > Options... > LibreOfficeDev > Accessibility" ... Miscellaneous Options Use text selection cursor in read-only text documents ( ) ( ) Allow animated graphics (x) ( ) Allow animaged text (x) ( ) Options for High Contrase Appearance Automatically detect high contrast mode of operating system ( ) ( ) Use automatic font color for screen display ( ) ( ) Use system colors for page previews (x) ( ) | | as found (SIGABRT) --+ | next test (SIGABRT) -------+ Most recently, with daily dbgutil bibisect version 2015-09-16, when I close the document the terminal output includes ... warn:legacy.osl:5015:1:editeng/source/items/frmitems.cxx:476: unknown MemberId warn:legacy.osl:5015:1:sw/source/core/access/accmap.cxx:1707: Frame map should be empty after disposing the root frame warn:legacy.osl:5015:1:sw/source/core/access/accmap.cxx:1724: Object map should be empty after disposing the root frame warn:legacy.osl:5015:1:sw/source/core/access/accmap.cxx:175: draw model listener is disposed /usr/include/c++/4.8/debug/vector:346:error: attempt to subscript container with out-of-bounds index 139898641233528, but container only holds 6 elements. Objects involved in the operation: sequence "this" @ 0x0x34aa288 { type = NSt7__debug6vectorIP11SfxListenerSaIS2_EEE; } Application Error Fatal exception: Signal 6 Just to confuse the issue (sigh!) ... (a) My screen only lets me enlarge the document window to almost one (footnote) line shorter that it was when I first reported the bug. (b) In an earlier test, I paused occasionally among the <page-down> keystrokes until the program repainted the document window. The program quit abruptly, i.e. before I had a chance to close the document. (c) Now, I have done <page-down> 40 times in quick tempo. The document window still shows the top of the document; soffice.bin has pegged the CPU and has accumulated 8 minutes of CPU time. The tail of the terminal output is ... warn:legacy.osl:5127:1:sw/source/core/access/acccontext.cxx:1154: child context should have a size warn:legacy.osl:5127:1:vcl/source/gdi/image.cxx:392: ImageAryData::Load: failed to load image 'cmd/lc_changecasetolower.png' warn:legacy.osl:5127:1:vcl/source/gdi/image.cxx:392: ImageAryData::Load: failed to load image 'cmd/lc_changecasetoupper.png' W: Unknown node under /registry/extlang: deprecated W: Unknown node under /registry/grandfathered: comments W: Unknown node under /registry/grandfathered: comments warn:legacy.osl:5127:1:editeng/source/items/frmitems.cxx:476: unknown MemberId warn:legacy.osl:5127:1:editeng/source/items/frmitems.cxx:476: unknown MemberId warn:legacy.osl:5127:1:sw/source/core/access/acccontext.cxx:305: Vis area of child is wrong. Did it exist already? ^C
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
I no longer see the bug in commit b157b82a, pulled around 2016-12-10 02:45 UTC, configured ... CC=ccache /usr/bin/gcc CXX=ccache /usr/bin/g++ --enable-option-checking=fatal --enable-dbgutil --enable-debug --without-system-postgresql --without-myspell-dicts --with-extra-buildid --without-doxygen --with-external-tar=/home/terry/lo_hacking/git/src --without-package-format built and running on debian-stretch. I am setting status RESOLVED WORKSFORME.