This bug was filed from the crash reporting server and is br-751dc08f-f54e-4a4d-9dad-58dd5de28507. ========================================= The crash occurred on exiting with the red cross and expecting to be given the option to save - which would have been accepted. This error has occurred twice since upgrading to my current version Version: 7.0.5.2 (x64) Build ID: 64390860c6cd0aca4beafafcfd84613dd9dfb63a CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: sv-SE (en_GB); UI: en-GB Calc: threaded On both occasions, I had just finished inserting rows into an auto filter array. The insertion was not over the entire row width of the array as I have created a multi purpose array for which I can sort on any "header" and simply insert new elements in the "correct" alpha sorted location without affecting the elements in the adjacent table. This is necessary to overcome an inability to have two independent tables adjacent to each other. It doesn't always crash when inserting in this manner. The first crash was totally destructive and task manager was required to shut the process down which obviated the normal crash report procedure. I have never reported a bug I this manner and so am uncertain whether I have duplicated a report. If that is the case then you have my apologies.
Not sure if it's relevant. I attempted to take a screen image of the crash pane so I could "log" the link for subsequent use but it appears the clipboard was locked by the incident as it wouldn't allow the simple [CTRL]+"V" to load it into Irfanview. Also Following a recent Win10 upgrade, many of my programs have fallen foul of a windows security feature preventing unauthorised access to a secured folder - my document folder🤦♂️. LO was impacted but subsequently authorised for access. Can't understand why LO wasn't automatically accepted by Windows -Do you need to submit some form of authorisation request to Microsoft?
Please test with a clean profile, Menu/Help/Restart in Safe Mode
(In reply to m.a.riosv from comment #2) > Please test with a clean profile, Menu/Help/Restart in Safe Mode After the latest automatically submitted crash report the restart went into some form of recovery mode but as a constantly cycling logo loop resulting with 6 LO processes running. Task manager was used to kill them but the subsequent "normal mode" restart had lost the installed optional extension - POWER DETECTIVE - which then resisted all efforts to reinstall. I had no alternative but to trash the profile and start again. I have, this morning, followed the original "insert cells" procedure and the eXit/save worked perfectly. Amusingly, when rebuilding my profile. I omitted the step of refusing startup tips. The first tip on opening LO this morning was "How to restart in safe mode to verify the integrity of the profile" - You must be Psychic😎. Whilst it now seems stable, it could indicate that the upgrade to 7.0.5.2 itself has the potential to corrupt an established user profile. Does an upgrade perform any modification of the current profile whilst being installed?
Sometimes the user profile gets corrupted for uncertain reasons, making LibreOffice to crash. Since this report was caused by a profile corruption, let's close it as RESOLVED WONTFIX
Clearly not the user profile. Identical circumstances have just resulted in another auto submission. Inserting a line into an autosort array saves successfully but produces the "crash & restore" panel which refuses to close and must be terminated by task manager. This time I completely ignored all missives to restart in protected mode and simply activated LibreCalc. It produced a plain blank sheet which I closed and then opened the file that had been "crashed" and it was perfect. Yet again, upon reopening the file, the Custom format manager indicated the array was now composed of two overlapping ranges which I corrected without issue. My autosort array is not what you might consider "normal" It is comprised of two adjacent arrays serving different data requirements. If I add a new element I always insert cells and shift down but only on the "half" of the array that contains the data which I wish to supplement. The data arrays are not of equal length so the right half has always-empty cells at the bottom rows. I can sort on any column to visualise the elements I'm interested in and then sort on the first column which reverts to two sorted lists adjacent to each other but of unequal rows. Why have a "complex" array? Because I don't want unique sheets per sortable array.
(In reply to Colin from comment #5) > > Identical circumstances have just resulted in another auto submission. > If somebody can advise me how to identify the auto submission from today's event I can link it to this item. I can't find it.
(In reply to Colin from comment #5) > Forgot to mention that yet again, the crash pane refused to accept any interaction and the LibreOffice process had to be killed with task manager.
Is it conceivable that this is related to 143049 where there is also an autosorted array with conditional colour formatting?
New crash auto report caf8e1ef-8c65-4b1d-99b8-5247db8db819 Sorry, both reports 143049 & 141299 appear to be open. Perhaps admin could consolidate and flag one as duplicate. I could do it but I'm not sure which one, nor of any further actions to be taken.
(In reply to Colin from comment #9) > New crash auto report > > caf8e1ef-8c65-4b1d-99b8-5247db8db819 > > Sorry, both reports 143049 & 141299 appear to be open. Perhaps admin could > consolidate and flag one as duplicate. > > I could do it but I'm not sure which one, nor of any further actions to be > taken. But the crashes are different.
(In reply to Colin from comment #9) > New crash auto report > > caf8e1ef-8c65-4b1d-99b8-5247db8db819 > > Sorry, both reports 143049 & 141299 appear to be open. Perhaps admin could > consolidate and flag one as duplicate. > > I could do it but I'm not sure which one, nor of any further actions to be > taken. That crash is reported in bug 143049 Putting this one back to RESOLVED WONTFIX