Description: assertion="!m_pFirst && !m_pLast && \"There are still indices registered\ Steps to Reproduce: 1. Open attachment 176549 [details] 2. CTRL+A (3x) 3. CTRL+X (table remains which probably off) Actual Results: Assertion Expected Results: Not so Reproducible: Always User Profile Reset: No Additional Info: Created attachment 176915 [details] bt with debug symbols On pc Debian x86-64 with master sources updated today, I got an assertion just after Ctrl-X.
Would be lovely to get a fix for bug 145930 first (if possible). As that bug requires a (certain) crasher to visible. People tend to fix the crasher, and leave the file recover saving broken :-(
FWIW a regular build does crash 1. Open the attached file 2. CTRL+A (3x) 3. CTRL+X (table remains which probably off) 4. CTRL+V 5. CTRL+V -> Crash Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 7e5af164b7d293dd410710bed411e1ca64bbecf7 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL
(In reply to Telesto from comment #2) > FWIW a regular build does crash > 1. Open the attached file > 2. CTRL+A (3x) > 3. CTRL+X (table remains which probably off) > 4. CTRL+V > 5. CTRL+V -> Crash > > Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community > Build ID: 7e5af164b7d293dd410710bed411e1ca64bbecf7 > CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win > Locale: nl-NL (nl_NL); UI: en-US > Calc: CL Not reproducible in Version: 7.2.2.2 (x86) / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 2; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: es-ES Calc: threaded
(In reply to Telesto from comment #2) > FWIW a regular build does crash > 1. Open the attached file > 2. CTRL+A (3x) > 3. CTRL+X (table remains which probably off) > 4. CTRL+V > 5. CTRL+V -> Crash > > Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community > Build ID: 7e5af164b7d293dd410710bed411e1ca64bbecf7 > CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win > Locale: nl-NL (nl_NL); UI: en-US > Calc: CL Repro Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: d47628f287f4377394c4ff488c433bfe254b6abe CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded
sw/qa/extras/ooxmlimport/data/line-rotation.docx (attached file) crashes with virtual SwIndexReg::~SwIndexReg(): Assertion `!m_pFirst && !m_pLast && "There are still indices registered"' failed. Steps to reproduce: 1. Open it 2. Select all 3 times without clicking anywhere 3. Copy 4. Paste 5. Undo
Created attachment 177643 [details] line-rotation.docx
(In reply to Telesto from comment #2) > FWIW a regular build does crash > 1. Open the attached file > 2. CTRL+A (3x) > 3. CTRL+X (table remains which probably off) > 4. CTRL+V > 5. CTRL+V -> Crash > > Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community > Build ID: 7e5af164b7d293dd410710bed411e1ca64bbecf7 > CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win > Locale: nl-NL (nl_NL); UI: en-US > Calc: CL Not Reproducible with a regular build Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: 31700036e517691d154701f4b8aeecb85cde607f CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: es-ES (es_ES.UTF-8); UI: en-US Calc: threaded Anyway, you should not mix crashes and asserts, they should be reported separately since asserts don't affect release builds
Meanwhile I found bug 146849 which is reproducible in a release build
Dear Telesto, 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