Description: Crash scrolling down in large file while still loading Steps to Reproduce: 1. Open the attached file 2. Scroll down to bottom starting after opening 3. Crash 4. If not -> File reload try again Actual Results: Crash Expected Results: No crash Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.0.0.alpha0+ (x64) Build ID: 52820b52b3bca45e2db527d1cc5f4488b2e0b9d0 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
Created attachment 163337 [details] BT without symbols
Created attachment 163338 [details] Example file
Created attachment 163339 [details] Screencast
confirm crash in Version: 7.1.0.0.alpha0+ Build ID: 1c584069a86e35b847f398b8bf78dce7428c2f63 CPU threads: 4; OS: Mac OS X 10.15.5; UI render: default; VCL: osx Locale: ru-RU (ru_RU.UTF-8); UI: en-US Calc: threaded
Reproduced in Version: 6.4.0.0.alpha1+ Build ID: 9bc848cf0d301aa57eabcffa101a1cf87bad6470 CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded oldest commit in 7.0 repo
and Version: 6.3.0.0.alpha1+ Build ID: c98b1f1cd43b3e109bcaf6324ef2d1f449b34099 CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded oldest commit in 6-4 bisect repo. I had to try 5 times before I got the crash. Really hard to reproduce and bisect
Not reproducible if all the changes are accepted/rejected, the file is save and reloaded. @Telesto, @Roman, could you please confirm ?
(In reply to Xisco Faulí from comment #7) > Not reproducible if all the changes are accepted/rejected, the file is save > and reloaded. > > @Telesto, @Roman, could you please confirm ? Think it more related to the content: see also has the same crash. So not directly tracking changes. it only needs some special arrangement or amount of text. There are lots of variables. Tracking changes working differently. Changes in timers. Difference in layout rendering. BT with symbols would be nice indeed. Bibisecting nearly impossible. Could go back to they ooo days. Timers of 4472 are so different it would even appear.
Crashed for me with 6.0. No repro with 5.4 as far I can tell
Created attachment 163442 [details] bt with debug symbols (gtk3) On pc Debian x86-64 with master sources updated today + gtk3 rendering, I scrolled the whole file, no crash. I had a crash when trying to close the file.
No crash with gen rendering.
(In reply to Julien Nabet from comment #11) > No crash with gen rendering. :-(. FWIW. you drag the scrollbar to the bottom? As in the screencast
Created attachment 163443 [details] BT with some symbol info
O FWIW, got three totally different BT's this is the region one.. also a Mouse-event.. and a SDR contract. So there are multiple bugs so run in one of those, without knowing which it actually is; or they are all related somehow
Created attachment 163444 [details] Different BT objectcontactofpageview.cxx
And I also reproduce this with a accepted all changes variant.. only less often (scrolls up faster etc). But not quite a surprise 1417 void vcl::Region::SetEmpty() 1418 { 1419 // reset all content 1420 mpB2DPolyPolygon.reset(); 1421 mpPolyPolygon.reset(); 1422 mpRegionBand.reset(); 1423 mbIsNull = false; 1424 } 1425 1426 Region& vcl::Region::operator=( const vcl::Region& ) = default; Resetting all content as it's probably still needed somewhere. I would say it's more co-incidence; timing element. Being at the wrong place at the wrong moment
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
No crash in Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 3e544b6938ee509a4f6df4c2e2996d71ce072506 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL threaded I'll close this one as WFM. Please reopen if you still have the problem