Description: Problem signature: Problem Event Name: APPCRASH Application Name: soffice.bin Application Version: 24.2.0.3 Application Timestamp: 65b6ac8b Fault Module Name: ucrtbase.DLL Fault Module Version: 10.0.14393.2990 Fault Module Timestamp: 5caeb96f Exception Code: 40000015 Exception Offset: 000000000006e01f OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional Information 1: e4c0 Additional Information 2: e4c0d3fcb7ff630ec44c5997a7378a14 Additional Information 3: cf83 Additional Information 4: cf83ede45a981f793121de3d41091358 Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt Steps to Reproduce: 1.Just open the file 2. 3. Actual Results: crash as seen and wants me to go see Microsoft Privacy policy for some reason Expected Results: nothing -- tried online search for fix as offered in crash window Reproducible: Always User Profile Reset: No Additional Info: It should just load and work as it does in Office 2010 and Apache.
Is it possible to attach a sample file for testing? If we cannot reproduce the issue, it won't be possible to figure out the problem.
Created attachment 192733 [details] Tax prep spreadsheet
Opens fine with Version: 24.2.1.1 (X86_64) / LibreOffice Community Build ID: 359ef544e625d2ffbfced462ab37bd593ca85fa7 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Please test in safe mode, Menu/Help/Restart in Safe Mode
I'm running Win 7 Pro 64 bit -- I have not been able to find that version for Windows. However it did load in Safe Mode.
(In reply to Tom Luoma from comment #4) > I'm running Win 7 Pro 64 bit -- I have not been able to find that version > for Windows. > However it did load in Safe Mode. You open LO > menu help > about; there is an icon to copy the info to the clipboard, so you can paste that info in your next comment to the report. FWIW, based on comment 0, my guess is that what crashed was the OS, rather than LO. If that is the case, it might not be so easy to replicate by other users. Seeing how slow attachment 192733 [details] gets loaded by LO (or by AOO for that matter), I might guess that some OS resources could be at some limit in your system, maybe? I would suggest a reboot of Windows 7, unloading things that are not really needed (at least for a test), and trying again with the same file(s).
huh -- odd and odder When I started LO there was a thumbnail of the file in ods format. It opens and appears complete. I guess when I opened it in safe mode the file got saved -- I did not save it. The ods loads fast-- maybe too fast -- I'm quite sure everything is there. However I happened on two tabs with display artifacts -- a tab labeled SCH1 Line20 and the next tab over. They are random vertical lines. So I launched AOO and opened the xlsx version (at the same time) - it has the exact same lines. I don't expect you see anything like that. Any ideas about this? At that point 33% of 16GB ram in use with both apps running and the file loaded. I then tried to load the xlsx again (LO only) and got the original crash. The drive is partitioned and these two apps are not on the root. Version: 24.2.0.3 (X86_64) / LibreOffice Community Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1 CPU threads: 8; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded I built this system a while back but it is quick enough. MSI MB, Samsung 960 M.2 500GB SSD, GTX 1060 6GB graphics, good box plenty cool. While watching Resource Monitor I loaded it all again -- no strain. It is a very complex spreadsheet. The guy did a hell of a job. I had been using earlier versions of this spreadsheet since 2018 on Office 2010 Pro. I never had a problem. But suddenly MS doesn't like my license after I moved stuff around on the disk and reloaded Office. I did load a version of this file late last year to estimate my taxes.
Additional note -- when I load it in AOO it tells me the file has links to other files and need to be updated. Also I expect the drawing artifacts may show up somewhere else on other hardware or OS.
Crap - I just realized the thumbnail ods LO loaded was from the test I ran on AOO.
(In reply to Tom Luoma from comment #6) > So I launched AOO and opened the xlsx version (at the same time) I would suggest not opening AOO and LO at the same time, or attempting to run 2 LO versions at the same time for that matter. That could be a possible reason for strange behaviors, user's profile corruption and even crashes. At this point I would suggest resetting your LO's user profile and retesting again, with the original xlsx file. At this point, if there is really a bug causing these strange behaviors, it would seem not so easy to replicate and thus isolate its cause.
I guess as a final comment -- the sequence Download latest LO and AOO Install LO -- run, load file, crash Install AOO -- run, load file, works -- make ods version to test load speed No user profile changes or mods of any sort made to either app Several reboots made in between various tests Started bug report and went thru sequence shown in comments Only ran both apps together when it was suggested LO might be loading my system Never ran two copies of LO at same time I renamed the User folder using Total Commander, restarted LO -- crashed as before. BTW -- the ods version has the same vertical line drawing artifacts in both LO and AOO I just copied original xlsx to a different partition (127GB free). Started Safe Mode and reset to factory (last option). LO crashed as before. Then copied file to LO directory (it is in a different partition -- 77GB free). Started Safe Mode with no changes -- crashed I went back to the original directory which has both versions. Opened ods file in Safe Mode -- OK -- Closed tried to open xlsx file in Safe Mode -- crashed. When I said earlier that it opened the file in Safe Mode I think I had screwed up and used the ods version.
Just to be clear, when you say that you open a file using Safe Mode… Do you mean the OS, or LO's Safe Mode? First, backup the file and perform all the tests with a copy, not the original. Do you have any clipboard manager? I would suggest closing any other program, including other LO documents, and use new Calc spreadsheet > menu Help > Restart in Safe Mode. Using the initial options/dialogue there, I would suggest first saving a backup of your settings/options/profile, and then reset _everything_. Then retest your file in LO's Safe Mode. FWIW, I have opened your file with no problems, both in a recent LO and AOO (not simultaneously). BTW, has this file ever had a password protection? Is it possible for you to try opening this file using a different OS? Perhaps there is a problem with LO and Windows 7. Have you ever tested opening this file with an older version of LO?
LO safe mode My dedicated clip/screen grabber is not currently loaded but Windows, Chrome etc do what I need. Why? I went into msconfig and shut down everything possible and rebooted. Tried to load the file -- no good. Did what you suggested -- no good. I can load any of my xls files one of which is 2.2MB -- but they are not nearly as complex and cross-linked. Done on Office 2000 I first started using a version of this file in 2018 -- less complete 2.3MB in size -- won't load either. The xlsx format forced me to look for a new app and I tried LO, AOO and I think Softmaker -- none worked with that 2018 file so I had to go and get Office 2010. No password -- The file is freely available from the listed site so there is no protection -- just the internal protected cells, etc. I'm out in the middle of nowhere since I retired -- would have to find a neighbor. I'm a long time techie in farm/ranch country. OK -- you loaded it. Are you using Linux or Windows (if so what version?) Do you see the vertical line artifacts on any of the tabs? When I loaded the 2018 in AOO they where there on tabs here and there-- black lines like felt marker. None of his files loaded in Office 2010 in last six years showed this. I appreciate all the help but it has been a rough few months. I don't need anymore stress and at this point I'll just go buy a copy of Office 2013, 16 or other. Or I might be able to run in ods file AOO made and use it or LO for this file -- that's if MS will let me reload my Office 2000 -- I like it best anyway. Thanks again.
Beware: any of the following options may generate slow reaction of LO. The only purpose of this comment is for testing, trying to narrow down the reason for the crash. I tested attachment 192733 [details] on Windows 10 before. I now tested it on a Windows 7 x86 (32 bits) VM. When I say I tested it I mean I opened it, without having any crash. I have not checked anything else. Perhaps you could test with different settings in Calc: menu Tools > Options > LibreOffice > View > (Graphics Output) ...such as disabling the use of Skia for all rendering, or without hardware acceleration. Please remember this may result in slow reactions, and it is only for testing. YMMV. There is also Calc menu Tools > Options > LibreOffice > OpenCL. Again, possible slowness, for test only, YMMV. Until someone else replicates the crash in some way, there is no other user to gather info.
Created attachment 192753 [details] Graphic Test Results from Tools/View
Created attachment 192754 [details] Crash Log File
Created attachment 192755 [details] GraphicsTestLogFile The list box will not display the lock files -- pasted below .~lock.23_1040-JAN24.xlsx# ,Tom-i7_64/Tom,Tom-i7_64,24.02.2024 17:19,file:///C:/Users/Tom/AppData/Roaming/LibreOffice/4; .~lock.Logfile.odt# ,Tom-i7_64/Tom,Tom-i7_64,24.02.2024 17:19,file:///C:/Users/Tom/AppData/Roaming/LibreOffice/4; Please note the file box (list box) display to attach files does not show the AppData subdir so I have to keep moving things around to attach them
My comments before the attachments has gone poof. I don't remember all of what I said other than I tried all the View options in various ways-- even forced SKIA-- and it did not seem slower.
For those that might be interested... Attachment 192753 [details] from comment 14 is a zip file containing more than 100 png's. Attachment 192754 [details] from comment 15 seems to be an empty odt file. Either the mime type is wrong, or this is some kind of mistake / wrong file. Attachment 192755 [details] from comment 16 provides some test results, starting by: Graphics Backend used: skia Passed Tests: 52 Quirky Tests: 51 Failed Tests: 1 Skipped Tests: 5 (In reply to Tom Luoma from comment #17) > I tried all the View options > in various ways-- even forced SKIA-- and it did not seem slower. Did you managed to open the xlsx file without crashing in any of your tests? Did you try with _no_ Skia rendering?
Sorry for the typo in my comment 18. Did you manage to open the xlsx file without crashing in any of your tests? Did you try with _no_ Skia rendering?
It never loaded I started by unchecking all the View>Graphics options and OpenCL and tested -- Then tested each by itself where possible starting with OpenCL -- And finally all the default settings with Force SKIA If I find the time today I'm going to try and update the NVIDIA drivers -- always a hairy task.
(In reply to Tom Luoma from comment #20) > It never loaded Does that mean that it always crashed? If, instead, nothing happened, then that would be the possible slowness I mentioned before.
It has always crashed -- both with the original xlsx and the ods created by AOO. It is very slow trying to load the xlsx and doesn't crash until it it gets to the end of the "loading bar". AOO which loads it is VERY slow -- it might be taking a couple of minutes -- I'll have to time it. And as I mentioned it also asks to update links to some files-- OD does not. I'm still trying to find time to update Nvidia -- mainly to see if those drawing artifacts go away. Another busy day on other things though.
Please let us know how you go after your driver update. And if you can, share a crash log as a simple text file to replace attachment 192754 [details].
After a driver update, if this still generates a crash – of the OS? of LO only? – I would suggest gathering info regarding both Skia and OpenCL in this specific Windows 7 system. BTW, without OpenCL, the procedure might take several (tens of) minutes. While the operation is carried out, LO might show as not responding, until the operation is completed. This is not exactly the same as LO crashing. Probably Stéphane would know which steps should be followed in order to gather the relevant info, for Skia and for OpenCL, under Windows 7.
Dear Tom Luoma, 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
Dear Tom Luoma, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp