Description: Reported by users here: https://ask.libreoffice.org/t/calc-7-5-0-3-for-windows-bsod/88511 In Calc 7.5.0.3, when copying a huge amount of data would cause BSOD in Windows 11, the error message was "page_fault_in_nonpaged_area". The tested ods file will be attached soon. In the ods file, column A-D are pure data, column E-F are formulas. When enabling the "Use hardware acceleration" in Tools - Options - LibreOffice - View, selecting cells including column E-F (for example, select A1:F32376) and hitting Ctrl-C would cause BSOD in Win11. Not happening in the following condition: - Selecting fewer data (for example, E1:F10) - Not selecting cells from column E and F (for example, selecting A1:D32376) - check "Force Skia software rendering" - In version 7.4.5.1, no such problem even enabling hardware acceleration Not happening in Linux (tested in Debian testing, but in my own box). Steps to Reproduce: 1. Open the attached file 2. Select data cell A1:F32376 3. Hit Ctrl-C Actual Results: Blue Screen of Death with message "page_fault_in_nonpaged_area" Expected Results: OS not crashed Reproducible: Always User Profile Reset: No Additional Info: Problematic version: Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 12; OS: Windows 10.0 Build 22621; UI render: default; VCL: win Locale: zh-TW (zh_TW); UI: zh-TW Calc: CL threaded Non-problematic version: Version: 7.4.5.1 (x64) / LibreOffice Community Build ID: 9c0871452b3918c1019dde9bfac75448afc4b57f CPU threads: 12; OS: Windows 10.0 Build 22621; UI render: default; VCL: win Locale: zh-TW (zh_TW); UI: zh-TW Calc: CL Graphic card information: NVIDIA GeForce GTX 1060 Driver version: 528.49 OS information: Windows 11 Professional 22H2 Installed: 2022/9/30 OS build: 22621.1265 體驗 Windows Feature Experience Pack 1000.22638.1000.0
Created attachment 185593 [details] test sample file which caused BSOD on win11
Not able to reproduce in: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d887b6a6fa2a572f48498839c5a68791c3196634 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded I was able to copy and paste said area. Can you please test in 7.5.1.2? Thank you!
(In reply to Stéphane Guillou (stragu) from comment #2) > Not able to reproduce in: > > Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community > Build ID: d887b6a6fa2a572f48498839c5a68791c3196634 > CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: default; VCL: win > Locale: en-GB (en_GB); UI: en-GB > Calc: threaded > > I was able to copy and paste said area. > > Can you please test in 7.5.1.2? > Thank you! According to the original reporter in https://ask.libreoffice.org/t/calc-7-5-0-3-for-windows-bsod/88511/3 The same BSOD with version 7.5.1.2 Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 12; OS: Windows 10.0 Build 22621; UI render: default; VCL: win Locale: zh-TW (zh_TW); UI: zh-TW Calc: CL threaded
[Automated Action] NeedInfo-To-Unconfirmed
No problem here with Win11. Franklin: it is not clear to me if you reproduce the problem. Do you? Version: 7.4.0.0.alpha1+ (x64) / LibreOffice Community Build ID: c94961c6869c34b3874d21cfaa5ec1488609acfe CPU threads: 2; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_FI); UI: en-US Calc: threaded Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 07aa8138db9bbaf222f2b7cea12a9f7d0a8192d7 CPU threads: 2; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_FI); UI: en-US Calc: threaded Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1b463f697405e64a03378fb38a32172c4d3c25e6 CPU threads: 2; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_FI); UI: en-US Calc: threaded
(In reply to Buovjaga from comment #5) > No problem here with Win11. > > Franklin: it is not clear to me if you reproduce the problem. Do you? No. I don't have any Windows system. What I've posted is from the original reporter on ask.lo
Dear Franklin Weng, 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