This bug was filed from the crash reporting server and is br-320f0af9-7362-4571-a8e5-0a1da33366c4. ========================================= I have recently moved onto a newer WIN 11 capable machine and all active files were transferred. CALC has been regularly crashing since the new implementation (Jan25) but this is only the second time it auto created a bug report (I didn't have time to capture the first one's details) There have been more than 50 crashes. I auto load specific sheet from shortcuts in the startup folder (Min 1 MAX 5) on startup and they "sit in the background" until my work stream gets to them. Often they have just disappeared without any interaction and sometimes I may have made a few entries prior to their demise. Sometimes I preemptively save [Ctrl]+S to reduce the impact of the inevitable crash. It always takes out every open CALC regardless of any prior interaction. I noticed from the listed reports that CALC hadn't featured so I hope it was the right thing to do to file a CALC bug. If not, my apologies for the additional clutter Let me know if you need a copy of MSInfo32.nfo - I have one dated 13/2/25 but if directed could take another immediately following any crash
Version: 7.5.9.2 (x86) / LibreOffice Community Build ID: cdeefe45c17511d326101eed8008ac4092f278a9 CPU threads: 12; OS: Windows 10.0 Build 26100; UI render: Skia/Vulkan; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded An untouched sheet I reloaded to get the ABOUT info crashed while I was adding these few lines :((
Colin, can you try to reset user profile? Thank you for reporting the bug. To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile (<https://wiki.documentfoundation.org/UserProfile>) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present. Also you are using a very old version of LibreOffice. 7.5.9 end of life was on Nov 30, 2023. You can try 24.8 (supported until June 12, 2025) or 25.2 (supported until Nov 30, 2025). Anyway, a reset to user profile is needed when using a new version.
(In reply to BogdanB from comment #2) > Colin, can you try to reset user profile? Can you advise me how to preserve a copy of the current profile for reversion should a reset prove ineffective and serve only to wreck all the personalisation that has been stable since 7.5.9.2. Once I am able to preserve a profile copy for reversion then that's the first thing I will do. > Also you are using a very old version of LibreOffice. 7.5.9 end of life was > on Nov 30, 2023. You can try 24.8 (supported until June 12, 2025) or 25.2 > (supported until Nov 30, 2025). Anyway, a reset to user profile is needed > when using a new version. See Bug145995 and bug160018 Yes it's an old version because the Defined Table Sorting bug introduced with everything after 7.5.9 wrecks worksheets that have worked fine since 2016. See outstanding Bug145995 Dec2021 and bug160018 Mar2024. I Can't upgrade until LO is stabilised. I have not accepted any upgrades since I had to revert to 7.5.9.2 so by your own definition - Anyway, a reset to user profile is needed when using a new version - is it still feasible to suspect my profile?
You have instructions in the link I provided to you Manual procedure (all versions) If you are using an old version of LibreOffice, or if the Help wizard procedure detailed above seems too complicated: Close LibreOffice including "QuickStart" in system tray. Find your user profile per information below, according to your operating system. Rename the folder /user to (for example) /user-old. Launch LibreOffice, a new /user folder will be created with factory settings. Test and see if the problem is gone. If the problem persists, you can restore the previous profile because it was not the cause of the problem. To do so, delete the newly created /user folder and give the renamed old one its former name /user back. If the problem is solved, it means that one or several configuration files were damaged. But it doesn't mean that the whole profile is dead. If you have heavily customized LibreOffice, you can still try to retrieve some parts of your configuration: as you have kept a backup (/user-old), copy the subfolders (one at a time), and restart LibreOffice to see if the issue comes back or not. You can therefore spot from where the issue comes. Look at the content of the profile (below), some are less prone to corruption than others.
(In reply to BogdanB from comment #4) > You have instructions in the link I provided to you > Sorry, missed it in my haste. Is it worth trying the "safe mode" restart first to see if it proves or disproves profile error? I have also noticed that if I have worked on a file(s) and successfully saved it(them) then it seems less prone to crashing during the remainder of the day - that's less prone NOT immune. I can disable the auto-start sheets to enable "Safe Start" and then invoke them to see if it makes a difference I can also confirm that when I installed 7.5.9.2 onto this machine, even though I copied the LO data files I stall needed to rebuild the UI Customisation so does that preclude the probability of a corrupt user profile?
(In reply to BogdanB from comment #2) > Colin, can you try to reset user profile? > I restarted in SAFE mode, worked a sheet, saved and rebooted the PC which appears to have resolved the issue. I only lost one or two mods to the Toolbars which I can live with(out) Does that change the status to RESOLVED or something else? I will leave that in your capable hands. Thanks for the help
(In reply to BogdanB from comment #2) > Colin, can you try to reset user profile? BTW this mornings first crash created https://crashreport.libreoffice.org/stats/crash_details/03b38f98-8d3b-4e86-adcc-8963ced0182a Does that need to be somehow "massaged" to link it to this report or expunged? Again, left it in your capable hands :)
Colin, I will let developers evaluate this. I understand from you that the crash still happened, and from the crash report website I understand that this crash still happens to 25.2 version.
(In reply to BogdanB from comment #8) > Colin, I will let developers evaluate this. I understand from you that the > crash still happened, and from the crash report website I understand that > this crash still happens to 25.2 version. It hasn't happened since midday yesterday nor at the most persistent early morning startup with a collection of auto-opens. The significant difference is that I never replaced the "SAFE MODE" removal of the permanent display of the "Form control" toolbar, I simply added the "Design mode" button to the ribbon. I removed a few more unused buttons from the ribbon which I think are added during the "standard" startup. I also have to modify the keyboard shortcuts to replace the "Insert date & insert time" functions with combinations suited to a Swedish keyboard used with the UK Locale. Hope that's not too much information (Red Herring).
@bogdanB A more precise update as it happened again today, creating https://crashreport.libreoffice.org/stats/crash_details/3c442302-8625-4693-baf5-2cd8461b5234 My user profile was rebuilt in an endeavour to isolate the cause of the earlier crash. The system functioned normally until I focused an auto-loaded sheet today. This sheet is characterised by having URL buttons on every line (1135 incrementing by 1 daily) linking to a local image source in addition to 7 more buttons in the “dashboard/header”. Immediately the daily buttons are created they are then modified to “Anchor & Fit” then “Fitted to Cell”. I have filed previous reports concerning the stability of the “A&F” processing which has certainly not been addressed up to my “old” version. Yesterday I had inadvertently inserted the URL link in the wrong place but hadn’t noticed this until I attempted the A&F + FtC – the button was missing and I simply assumed a glitch and created it correctly. Today I discovered the incorrect location of the button, the left of which was “nubbed” right up against the right margin of a concealed column. I attempted to focus and delete the button but the system wouldn’t permit the focus. I re-focused it and then it crashed. This is the first time the crash has occurred in conjunction with an immediate action I had instigated. Upon recovery I “unhid” the column and it permitted the deletion but the system crashed later in the process without creating a report. I shut down and restarted and it has been “stable” for the last 2 hours.
@BogdanB A Eureka moment: Perhaps you can help define whether it is a bug or just an exception that will never be addressed. The short version, I conducted numerous experiments and generated the following auto-reports:- https://crashreport.libreoffice.org/stats/crash_details/6337dd57-02fb-420a-9779-47f2263f5ec3 https://crashreport.libreoffice.org/stats/crash_details/320d446d-6376-4476-b86b-bf4bc00ef8e5 https://crashreport.libreoffice.org/stats/crash_details/276e3a63-2890-46c9-9561-1f7683149ed1 https://crashreport.libreoffice.org/stats/crash_details/5905d7d6-fb30-42f7-b4d1-5b96df9c7748 I have just realised that one of my actions on the day the fault manifested was to insert a cell in 1 column of a 4 column filtered array on another less frequently utilised sheet in the workbook. I immediately realised it would "unsync" that array - so I inserted three more cells in their appropriate locations to re-balance the array. I don't recall whether this was an immediate remediation or whether I realised a few moments later and went back to rectify it. Today's experiments prompted me to remember that event so I have simply used the filter to sort the array and the problem has been expunged. Had I added the entry to the bottom and re-sorted the array it would probably never have manifested itself. That does indicate that there is a problem when a user inserts elements into the middle of an array rather than adding them to the bottom of the array and using the "sort" in the filter context pane to correctly place them. It's also uncertain whether the act of inserting one cell first rather than all cells on that row as opposed to inserting an entire row instead of appending and sorting is the culprit. This is where you earn your money and make the appropriate assessment :)
Colin, can you provide a simple document, with no sensitive data into it, in order for us to test this case? Also, with some simple explanation how to reproduce the bug. Thanks.
Created attachment 199334 [details] Cutdown ods to demonstrate LoO Crash I removed some sheets and experienced crashes as the tabs were deleted. This is the most recent; https://crashreport.libreoffice.org/stats/crash_details/d9d4800a-4310-4c8b-9013-932ff302025a 1. Sheet MultiVowel insert a single cell anywhere in the first column - "6982" is a volatile count - with [Ctrl]+[+] and accept shift cells down. It would be prudent to insert below a row that contains "yes" in both the rightmost cells 2. Enter any 5 letter word and REMEMBER the insert location 3. Exit the sheet by selecting another tab 4. Return to MultiVowel 5. Select the three adjacent cells and insert cells with [Ctrl]+[+] and accept shift cells down 6. Drag Fill the formula in column "Vowels" into the newly created cell 7. Type "yes" into the newly created cell in Column "Wordle" 8. Copy the formula in any "Used" cell into the newly created "used" cell location 9. Close and save the document 10.Open the document and any other document you may have lying around 11.Enter random data into either document - IF IT GETS THAT FAR 12.Repeat 11 until a crash 13.Open "Wordle and then on sheet "MultiVowel" Sort on Column "6982" 14. Verify the document now appears to be stable.
Note: the new crash experienced whilst trying to create this ods is not the same crash condition. The fault report would simply be "attempting to prune the submitted sheet to enable submission" Nothing in the full sheet is confidential - let me know if you need that it's 2MB
(In reply to BogdanB from comment #12) > Colin, can you provide a simple document, with no sensitive data into it, in > order for us to test this case? > Hi again, Bogdan, That sheet seems to be inherently unstable AND destabilising. If other workbooks are active it will crash all of them at the slightest provocation. If it is a singleton then it may crash when a tab is removed or when an attempt is made to enter data into a cell - it seems quite random. The "master" sheet I retained seems to be more stable than the test version having "sorted" all arrays using the filters. Some errors may be due to the location of "linked" files not being in their correct relative locations when the document is copied to the desktop (and your own computer). Something even more significant is that the original workbook is the source for at least two other bug reports relating to the loss or presentation of URL Buttons. BUG142251, BUG148717 The workbook you now have is also a demonstration of the URL button's failing integrity. If you scan the "Performance" sheet ColF (195 a counter) with all the URL buttons linking to the stored images you will notice how despite their definition as "Anchored and resize & Fit to cell" they do not all comply. Assess F3:F19 which initially looks to be compliant but that's not cell fit - it's just a close approximation Assess F20:F134 Not even a close approximation Assess F135 Same as the first cluster Assess F136:F179 identical to the second cluster At F893 it reverts to the "almost correct" status AT F910 IT presents according to the user's instructions Some of those anomalies may have occurred as the direct result of unhiding ColB and or G:I when amendments were being made to the "hidden" formulae. The cluster F910:F is likely the last time I amended those hidden formulae (and tired of working my way through row by row to remediate the errors. The URL buttons do not resize when the column F metrics change Is it conceivable that the "flaky" URL button management AND the badly inserted row into a filtered array may be combining to create the anomaly? Just some thoughts on the issue. If I'm more hindrance than help tell me - I promise not to cry ;).
Another Trigger The moment the %screen magnification parameter (Bottom right corner say 100%) is left clicked then it crashes. This occurred when it was the first action taken on the newly opened sheet (1 of 2 auto starts) and also after I had: 1. Recovered both workbooks (To ascertain whether it would generate a crash report - NO) 2. Fully processed the workbook 3. Saved the workbook with [Ctrl] + [S] 4. Selected the resize parameter Not sure if it's relevant but as I'm typing this report, the second auto sheet which was recovered to the top layer of my second monitor just unfocused itself and went to the bottom layer of the screen. Is there some kind of keyboard shortcut for that which I may have inadvertently activated?