Description: Quick scrolling in a spreadsheet with many rows (2000) causes a "Libre Calc has stopped working" crash. It doesn't require a restart of the computer. Steps to Reproduce: 1. new spreadsheet with no data (no need to save) 2. scroll down until about 2000 rows have been created 3. scroll back to the top 2. left click the vertical scroll handle and scroll up and down rapidly Actual Results: The crash occurs sporadically during normal operation but if you scroll up and down quickly and aggressively, the crash will occur within seconds. Expected Results: It shouldn't crash Reproducible: Always User Profile Reset: No Additional Info: Hopefully scroll to the desired location. Alternatively it could say "whoa - slow down, big guy, getting there is half of the fun"
I didn't mean to set it to normal severity - it's major or critical due to data loss but now it won't let me change that.
Please test with a clean profile, Menu/Help/Restart in Safe Mode
Here's what I did: 1. restart in safe mode and choose continue in safe mode [unable to reproduce crash] 2. restart in safe mode and this time select Reset to factory setting with both boxes checked, then apply changes and restart [now the bug returns] 3. restart in safe mode and this time choose configure and disable hardware acceleration, then apply changes and restart [unable to reproduce crash] I didn't know I had any hardware acceleration but that seems to have been the issue. Thanks.
[Automated Action] NeedInfo-To-Unconfirmed
The bug description reminds me of bug 150190
What's your precise Windows version? (do you confirm you use LO 32 bits on a Windows 32 bits?) Could you follow this https://wiki.documentfoundation.org/QA/FirstSteps#Graphics-related_issues_.28_Skia_.29 ? If after having checked you got last graphic driver, you still reproduce this, info about graphic card would be useful. Also, if it's possible to get a backtrace (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace), it would be useful.
I guess we may mark duplicate. Please add requested info here and to other bug. *** This bug has been marked as a duplicate of bug 150190 ***
Consolidating duplicates on older bug 149527 *** This bug has been marked as a duplicate of bug 149527 ***