This bug was filed from the crash reporting server and is br-5568e4c3-d16b-4615-967e-cf336f8daf1d. ========================================= Build: 184fe81b8c8c30d8b5082578aee2fed2ea847c01 I opened a Word doc (.docx) using right-click/Open With/Libre Writer. I edited the document and then 'x'd out, expecting the popup asking if I wanted to save using .odt format. It froze and was not responding. I checked Task Manager to see if there was something else causing memory, cpu or disk issues. From the graph, it looked like there HAD been, but that there were no issues currently. I checked running processes, and saw that Microsoft Word was running (which I did not expect, since I did not open it in Word). This is an older laptop, and does have some performance issues. So I stopped several Runtime Broker processes, the Word process, and a couple of others that I don't remember. Machine info: OS Name Microsoft Windows 10 Home Version 10.0.19045 Build 19045 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name LORETTAOLDPC System Manufacturer Hewlett-Packard System Model HP ENVY 15 Notebook PC System Type x64-based PC System SKU G0T55AV Processor Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz, 2501 Mhz, 4 Core(s), 8 Logical Processor(s) BIOS Version/Date Insyde F.34, 12/19/2014 SMBIOS Version 2.8 Embedded Controller Version 77.53 BIOS Mode UEFI BaseBoard Manufacturer Hewlett-Packard BaseBoard Product 2290 BaseBoard Version 77.35 Platform Role Mobile Secure Boot State On PCR7 Configuration Binding Not Possible Windows Directory C:\WINDOWS System Directory C:\WINDOWS\system32 Boot Device \Device\HarddiskVolume2 Locale United States Hardware Abstraction Layer Version = "10.0.19041.2251" User Name LORETTAOLDPC\Loretta Time Zone Pacific Standard Time Installed Physical Memory (RAM) 8.00 GB Total Physical Memory 7.93 GB Available Physical Memory 3.16 GB Total Virtual Memory 10.8 GB Available Virtual Memory 3.77 GB Page File Space 2.84 GB Page File C:\pagefile.sys Kernel DMA Protection Off Virtualization-based security Not enabled Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, Disabled by policy, TPM is not usable Hyper-V - VM Monitor Mode Extensions Yes Hyper-V - Second Level Address Translation Extensions Yes Hyper-V - Virtualization Enabled in Firmware Yes Hyper-V - Data Execution Protection Yes
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Created attachment 183891 [details] Document I was working on when Writer crashed I previously said the document was a .docx. I can see now it was actually a .doc. Also, I forgot to mention previously that I had sent the document to the printer at some point prior to it crashing (in case that also helps).
In a quick test with the doc, I could not reproduce, but in the crash report site I see reports for the same signature for Version: 7.5.1.2, so looks like this is still valid. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 0484a9a3f5e2ecb678f6fb41bbb251529e89c00d 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
Could not reproduce either, with 7.3.0.3, 7.4.5.1 on Windows 10. (I tried printing beforehand too.) Could you pleases share your version information copied from Help > About LibreOffice, and see if you can possibly figure out a consistent way to reproduce the crash? Thank you!
Dear Loretta, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
You can go ahead and close this. I have been unable to reproduce it and have now upgraded to a different laptop as well. I think I have also recently upgraded to a new version of LibreOffice. If it happens again, I'll just report it again.
The signature shows crashes from 7.6.0 still: https://crashreport.libreoffice.org/stats/signature/SwCursor::UpDown(bool,unsigned%20short,Point%20const%20*,__int64,SwRootFrame%20&)