Created attachment 157915 [details] file to repro caption undo/redo assert Assert is: sw/source/core/bastyp/index.cxx:226: virtual SwIndexReg::~SwIndexReg(): Assertion `!m_pFirst && !m_pLast && "There are still indices registered"' failed. I noticed this in version 7.0 while working on an enhancement to insert captions from the Navigator Tables context menu. I've also replicated in: Version: 6.4.1.0.0+ Build ID: 7bfe30c2a1c67961777ff52f20eac30a164e8340 CPU threads: 4; OS: Linux 5.0; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded Attached file contains the steps to repro.
Created attachment 157931 [details] bt with debug symbols On pc Debian x86-64 with master sources updated today, I could reproduce this.
This assert is easily seen with patch applied that adds insert caption menu item to Navigator table context menu. https://gerrit.libreoffice.org/c/core/+/88828
Lacking a debug build.. is this still present? I can't reproduce similar bug (which should cause a crash)... However lacking a debug build
Created attachment 168359 [details] bt with debug symbols Just to give an update but I think it's similar to the previous bt.
Still present Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: fbf739198aa7f02975d531521c6525073783c7f1 CPU threads: 8; OS: Mac OS X 12.2.1; UI render: Skia/Metal; VCL: osx Locale: nl-NL (nl_NL.UTF-8); UI: en-US Calc: threaded
I DO NOT reproduce in: Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded I followed the instructions in the ODT (reproduced below). After Step 6, nothing happened. - - - 0. Open attachment 157915 [details]. 1) Open F5 Navigator 2) Right click on first table, select Insert Caption… and enter a caption 3) Right click on second table, select Insert Caption… and enter a caption 4) Undo Undo Redo Redo 5) Double click on Table1 in Navigator 6) Undo Undo Redo Redo Result: sw/source/core/bastyp/index.cxx:226: virtual SwIndexReg::~SwIndexReg(): Assertion `!m_pFirst && !m_pLast && "There are still indices registered"' failed.
(In reply to Tex2002ans from comment #6) > I DO NOT reproduce in: > > Version: 7.6.4.1 (X86_64) / LibreOffice Community > Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 > CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: > win > Locale: en-US (en_US); UI: en-US > Calc: CL threaded > > I followed the instructions in the ODT (reproduced below). > > After Step 6, nothing happened. Thanks for testing. I think asserts are only active in debug builds. That is probably why nothing happened for you.
Created attachment 191958 [details] bt with debug symbols On pc Debian x86-64 with master sources updated today, I gave a new try and still got an assert.
> I think asserts are only active in debug builds. That is probably why nothing happened for you. Ahhh, okay. Thanks for the info. So a debug-only issue. Strange. Well, always good to poke at the backlog. And I'll have to keep an eye out for Crash-Asserts in the future. :) (I just searched, then was just randomly picking and choosing some older still-open bugs to retest.)
Dear Jim Raykowski, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from https://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: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still present: Version: 26.8.0.0.alpha0+ (X86_64) Build ID: 9cdb58822849805ca939e1079b01262e75a96bf2 CPU threads: 2; OS: Linux 6.14; UI render: default; VCL: x11 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded