Description: _CxxUnregisterExceptionObject VCRUNTIME140 after _RTDynamicCast related to SwViewShell::SetEndActionByVirDev Steps to Reproduce: 1. open the attached file 2. Go to page 18 3. Enter the page + press backspace 4. Delete the page break Use very sleepy (or a flame graph) to see what's being done Actual Results: 30% of 10 second time frame spend in CxxUnregisterExceptionObject (did only a partial trace) Expected Results: An exception doesn't sound optimal & spending a lot of CPU time in it (making stuff slow) makes it worse Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.0.0.alpha0+ (x64) Build ID: c48e4d795e37f23b71d647247590807ab9e52223 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 also in Version: 6.0.5.0.0+ Build ID: 15ea1cda0b3c37ff944ad9a239b7ed453e8b0591 CPU threads: 4; OS: Windows 6.3; UI render: default; Locale: nl-NL (nl_NL); Calc: CL and in Versie: 5.2.4.2 Build ID: 3d5603e1122f0f102b62521720ab13a38a4e0eb0 CPU Threads: 4; Versie besturingssysteem:Windows 6.2; UI Render: standaard; Locale: nl-NL (nl_NL); Calc: CL and in 5.0.6.3 but not in (and being fast too) Versie: 4.4.7.2 Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600 Locale: nl_NL
Created attachment 162632 [details] Example file
Created attachment 162721 [details] BT with symbols VTune Profiler based on x39 build Part 1
Created attachment 162722 [details] BT with symbols VTune Profiler based on x39 build Part 2
LayoutIdle activity
Doesn't feel like an actual problem in practice. I do see it recounting the words and characters in the status bar because it is a huge document. Maybe someone can evaluate it more deeply. Version: 7.2.0.0.alpha0+ (x64) Build ID: cb084f475db33a2cfc62bc9c8de37b8c3c87b3c7 CPU threads: 2; OS: Windows 10.0 Build 19042; UI render: default; VCL: win Locale: fi-FI (fi_FI); UI: en-US Calc: threaded
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